Triple
T35177360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimmerioi |
E1015745
|
entity |
| Predicate | locatedInHistorical |
P193823
|
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: [Kimmerioi, locatedInHistorical, Eurasian steppe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInHistorical Context triple: [Kimmerioi, locatedInHistorical, Eurasian steppe]
-
A.
locatedInHistoricSite
Indicates that an entity is situated within or on the grounds of a place officially recognized as a historic site.
-
B.
locatedInHistoricContext
Indicates that an entity is situated within or associated with a historically significant setting, period, or environment.
-
C.
historicallyPlacedIn
chosen
Indicates that an entity was located or situated in a particular place during a specific historical period or context.
-
D.
historicallyLocatedNear
Indicates that, in a historical context, one entity was geographically situated close to another entity.
-
E.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37fb1757bc81909365f66fb30f2380 |
completed | June 21, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.