Triple
T3701204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demetrias |
E78580
|
entity |
| Predicate | locatedInModern |
P43602
|
FINISHED |
| Object | regional unit of Magnesia |
—
|
LITERAL 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: regional unit of Magnesia | Statement: [Demetrias, locatedInModern, regional unit of Magnesia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInModern Context triple: [Demetrias, locatedInModern, regional unit of Magnesia]
-
A.
locatedInModernAdministrativeRegion
Indicates that an entity is geographically situated within the boundaries of a current, officially recognized administrative region.
-
B.
locatedInModernState
Indicates that one entity is geographically situated within the boundaries of a specified contemporary nation-state.
-
C.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
hasModernLocation
chosen
Indicates that an entity is currently situated in, or corresponds to, a specified modern geographic or administrative location.
-
E.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
- F. None of above.
Provenance (3 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc547c1848190a1ece46c59b7c43d |
completed | March 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.