Triple
T26198517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charaideo |
E655169
|
entity |
| Predicate | laterReplacedByCapital |
P30709
|
FINISHED |
| Object | Garhgaon |
—
|
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: Garhgaon | Statement: [Charaideo, laterReplacedByCapital, Garhgaon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterReplacedByCapital Context triple: [Charaideo, laterReplacedByCapital, Garhgaon]
-
A.
isPlannedToBeReplacedAsCapitalBy
Indicates that one capital city is intended or scheduled to be superseded by another as the official capital.
-
B.
succeededAsCapitalBy
chosen
Indicates that one capital city has been replaced by another as the official capital of a political entity.
-
C.
formerCapitalOf
Indicates that a place once served as the capital of another entity (such as a country or region) but no longer holds that status.
-
D.
replacesCapitalCity
Indicates that one capital city is substituted for or takes over the role of another as the official capital.
-
E.
capitalLaterKnownAs
Indicates that an entity served as a capital city under one name at a given time and was later known by a different name.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 26, 2026, 8:47 p.m.