Triple
T1384503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allahabad |
E29812
|
entity |
| Predicate | stateCapitalRole |
P20741
|
FINISHED |
| Object | former capital of United Provinces |
—
|
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: former capital of United Provinces | Statement: [Allahabad, stateCapitalRole, former capital of United Provinces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateCapitalRole Context triple: [Allahabad, stateCapitalRole, former capital of United Provinces]
-
A.
countryCapitalRole
Indicates that one entity serves as the capital city of a given country, representing its primary administrative or governmental center.
-
B.
stateCapitalFunction
chosen
Indicates that one location serves as the official capital city and primary seat of government for a given state.
-
C.
governingStateCapital
Indicates that a state serves as the governing political authority over the specified capital city.
-
D.
stateCapitalRegion
Indicates that a region serves as the capital area or administrative seat for a particular state.
-
E.
regionCapital
Indicates that one entity is the capital city or administrative center of a specified region.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c33896548190b44f70c9aaaed9b6 |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befe343c81909f758440a531b5be |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.