Triple
T31752135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salt Lake Buzz |
E810451
|
entity |
| Predicate | endUseOfName |
P172507
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Salt Lake Buzz, endUseOfName, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endUseOfName Context triple: [Salt Lake Buzz, endUseOfName, 2000]
-
A.
endName
Indicates that one entity serves as the ending or final name/designation associated with another entity.
-
B.
usesNameDueTo
Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
-
C.
nameUsedFor
Indicates that a particular name is used to refer to or designate a given entity.
-
D.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
E.
nameUsedToAvoid
Indicates that one entity uses a particular name or designation in order to avoid another entity or an unwanted situation involving that entity.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:28 p.m.