Triple
T37512338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caldeum |
E932546
|
entity |
| Predicate | replacedCity |
P43447
|
FINISHED |
| Object | Viz-jun as capital of Kehjistan |
—
|
NE NERFINISHED |
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: Viz-jun as capital of Kehjistan | Statement: [Caldeum, replacedCity, Viz-jun as capital of Kehjistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedCity Context triple: [Caldeum, replacedCity, Viz-jun as capital of Kehjistan]
-
A.
replacesCapitalCity
chosen
Indicates that one capital city is substituted for or takes over the role of another as the official capital.
-
B.
isPlannedToBeReplacedAsCapitalBy
Indicates that one capital city is intended or scheduled to be superseded by another as the official capital.
-
C.
cityAfterRelocation
Indicates the city where an entity is located after it has been moved or relocated from a previous place.
-
D.
hostCityRenamed
Indicates that the city hosting an event has undergone a name change from its previous official designation.
-
E.
hasNearbyCityRenamedIn
Indicates that a nearby city underwent a renaming event during a specified time or within a particular temporal context.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 3, 2026, 4:17 p.m.