Triple
T27961158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah Territorial Statehouse |
E704578
|
entity |
| Predicate | usedAsCapitolFrom |
P180312
|
FINISHED |
| Object | 1855 |
—
|
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: 1855 | Statement: [Utah Territorial Statehouse, usedAsCapitolFrom, 1855]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCapitolFrom Context triple: [Utah Territorial Statehouse, usedAsCapitolFrom, 1855]
-
A.
servedAsUSCapitalFrom
Indicates that a location functioned as the capital of the United States during a specified time period.
-
B.
servedAsNationalCapitalFrom
Indicates that a place functioned as the national capital of a country or political entity during a specified time period.
-
C.
usedForCapitalOf
Indicates that something serves as the capital city or primary administrative center of a specified political or geographic entity.
-
D.
wasDeFactoCapitalOf
Indicates that a place functioned in practice as the capital of a political entity, even if it was not officially designated as such.
-
E.
servedAsUSCapitalUntil
Indicates that a place functioned as the capital of the United States up to a specified end date.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
| PDg | Predicate description generation | batch_69f73adfd9a081908adae6bd59dfefb9 |
completed | May 3, 2026, 12:09 p.m. |
Created at: April 27, 2026, 7:31 p.m.