Triple
T33366753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UT |
E854376
|
entity |
| Predicate | hasAssociatedStateCapital |
P33213
|
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: [UT, hasAssociatedStateCapital, Salt Lake City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedStateCapital Context triple: [UT, hasAssociatedStateCapital, Salt Lake City]
-
A.
isStateCapital
Indicates that a city serves as the official capital of a given state.
-
B.
governingStateCapital
Indicates that a state serves as the governing political authority over the specified capital city.
-
C.
stateCapitalStatus
chosen
Indicates that an entity serves as the official capital city of a specified state or state-level administrative region.
-
D.
hasCapitalOfContainingState
Indicates that a capital city is the official capital of a state that geographically contains a given area or entity.
-
E.
hasBorderingStateCapital
Indicates that one state capital city is directly adjacent to or shares a border with another state capital city.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 1:35 a.m.