Triple
T26557931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vikramaditya |
E666161
|
entity |
| Predicate | legendaryCapital |
P160636
|
FINISHED |
| Object | Ujjain |
—
|
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: Ujjain | Statement: [Vikramaditya, legendaryCapital, Ujjain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legendaryCapital Context triple: [Vikramaditya, legendaryCapital, Ujjain]
-
A.
traditionalCapital
Indicates that a location serves as the customary or historically recognized capital of a region, people, or polity, regardless of its current official capital status.
-
B.
capitalRenamedFrom
Indicates that a capital city previously had a different name, specifying the former name from which it was renamed.
-
C.
capitalRenamedTo
Indicates that a place’s status or name as a capital city has been changed to a new capital designation or name.
-
D.
capitalSince
Indicates that an entity has served as the capital of another entity starting from a specified point in time.
-
E.
capitalDuringExistence
Indicates that a specified place served as the capital of an entity for some or all of the time that entity existed.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614697efc81909cba4b98b198b27e |
completed | May 2, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 27, 2026, 1:51 a.m.