Triple
T31752134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salt Lake Buzz |
E810451
|
entity |
| Predicate | startUseOfName |
P199486
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Salt Lake Buzz, startUseOfName, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startUseOfName Context triple: [Salt Lake Buzz, startUseOfName, 1994]
-
A.
endUseOfName
Indicates that one entity stops using or ceases to be identified by a particular name in relation to another entity or context.
-
B.
nameUsageRegister
Indicates the stylistic or social register in which a name is typically used (e.g., formal, informal, slang, archaic).
-
C.
importName
Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
-
D.
usesNameDueTo
Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
-
E.
incorrectInformalUsageOfName
Indicates that one entity uses another entity’s name in an informal context in a way that is considered incorrect or inappropriate.
- 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_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
| PDg | Predicate description generation | batch_69ff3e16527c81908c8d89da704ce012 |
completed | May 9, 2026, 2 p.m. |
Created at: April 30, 2026, 11:28 p.m.