Triple
T27961172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah Territorial Statehouse |
E704578
|
entity |
| Predicate | capitolMovedTo |
P19570
|
FINISHED |
| Object | Salt Lake City |
—
|
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: Salt Lake City | Statement: [Utah Territorial Statehouse, capitolMovedTo, Salt Lake City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitolMovedTo Context triple: [Utah Territorial Statehouse, capitolMovedTo, Salt Lake City]
-
A.
relocatedToWashingtonYear
Indicates the year in which an entity moved or was transferred to Washington as its new location.
-
B.
servedAsUSCapitalUntil
Indicates that a place functioned as the capital of the United States up to a specified end date.
-
C.
inauguratedAsCapital
Indicates that a place was officially declared and established as the capital of a political or administrative entity.
-
D.
laterSeatOfGovernment
chosen
Indicates that the referenced place served as a subsequent seat of government for the same political entity after an earlier one.
-
E.
headquartersMovedOn
Indicates that the location of an entity’s headquarters changed on a specific date or point in time.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 27, 2026, 7:31 p.m.