Triple
T21116023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Median kings |
E520300
|
entity |
| Predicate | usedCity |
P142915
|
FINISHED |
| Object | Ecbatana as royal residence |
—
|
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: Ecbatana as royal residence | Statement: [Median kings, usedCity, Ecbatana as royal residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedCity Context triple: [Median kings, usedCity, Ecbatana as royal residence]
-
A.
usedInCity
Indicates that something is utilized, applied, or operates within the context or boundaries of a particular city.
-
B.
usualCity
Indicates that a city is the standard, typical, or commonly associated city for a given entity (such as a person, organization, or activity).
-
C.
representedCity
Indicates that an entity serves as the official representative or proxy for a particular city.
-
D.
primaryUseCity
Indicates that a city is the main or principal location where something (such as a service, facility, or entity) is primarily used or operates.
-
E.
hadCity
Indicates that an entity was formerly associated with or located in a particular city.
- F. None of above. chosen
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_69e0b509a318819092fbbcb21d1fe603 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72106a3b48190a0efa51a74ae21f0 |
completed | April 21, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:55 p.m.