Triple
T33104764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Indiana |
E847155
|
entity |
| Predicate | laterStateCapital |
P200991
|
FINISHED |
| Object | Indianapolis, Indiana |
—
|
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: Indianapolis, Indiana | Statement: [History of Indiana, laterStateCapital, Indianapolis, Indiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterStateCapital Context triple: [History of Indiana, laterStateCapital, Indianapolis, Indiana]
-
A.
capitalOfNewState
Indicates that a city serves as the official capital of a newly established or newly recognized state.
-
B.
wasStateCapitalOf
Indicates that a city previously served as the official capital of a specified state or equivalent political region.
-
C.
governingStateCapital
Indicates that a state serves as the governing political authority over the specified capital city.
-
D.
capitalOfDefeatedState
Indicates that one entity is the capital city of a state that has been defeated, typically in a conflict or war.
-
E.
capitalOfMajorState
Indicates that one location serves as the primary capital city of a major state or significant administrative region.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
| PDg | Predicate description generation | batch_69ffc082a4e881908a92313d2c755afe |
completed | May 9, 2026, 11:17 p.m. |
Created at: May 1, 2026, 1:26 a.m.