Triple
T34347059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kangly tribe |
E881462
|
entity |
| Predicate | associatedMacroRegion |
P86016
|
FINISHED |
| Object | Eurasian Steppe |
E47140
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Eurasian Steppe | Statement: [Kangly tribe, associatedMacroRegion, Eurasian Steppe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMacroRegion Context triple: [Kangly tribe, associatedMacroRegion, Eurasian Steppe]
-
A.
belongsToEconomicMacroregion
Indicates that one economic region or area is part of, or classified within, a larger economic macroregion.
-
B.
associatedRegionFeature
Indicates that something is linked or connected to a particular geographic or regional feature.
-
C.
associatedAdministrativeRegion
Indicates that an entity is linked to, or falls under the jurisdiction of, a particular administrative region.
-
D.
locatedInPresentDayMacroRegion
Indicates that an entity is situated within the boundaries of a specified large-scale geographic or administrative region as defined in the present day.
-
E.
regionOfAssociation
chosen
Indicates a broader geographic or spatial area with which an entity is functionally, contextually, or organizationally associated.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37360b132c8190be647c0c88d565a0 |
completed | June 21, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:58 a.m.