Triple
T27961159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah Territorial Statehouse |
E704578
|
entity |
| Predicate | usedAsCapitolUntil |
P180413
|
FINISHED |
| Object | 1856 |
—
|
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: 1856 | Statement: [Utah Territorial Statehouse, usedAsCapitolUntil, 1856]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCapitolUntil Context triple: [Utah Territorial Statehouse, usedAsCapitolUntil, 1856]
-
A.
usedAsCapitolFrom
Indicates that a location served as the official capital of a political or administrative entity starting from a specified point in time.
-
B.
servedAsUSCapitalUntil
Indicates that a place functioned as the capital of the United States up to a specified end date.
-
C.
servedAsStateCapitalUntil
Indicates that a location functioned as the official capital of a state up to a specified end date.
-
D.
servedAsNationalCapitalUntil
Indicates that a place functioned as the national capital of a country or state up to a specified end date, after which it no longer held that status.
-
E.
servedAsUSCapitalFrom
Indicates that a location functioned as the capital of the United States during a specified time period.
- 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_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: April 27, 2026, 7:31 p.m.