Triple
T4845492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salt Palace |
E108277
|
entity |
| Predicate | siteSubsequentUse |
P14701
|
FINISHED |
| Object | Salt Palace Convention Center expansion |
—
|
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: Salt Palace Convention Center expansion | Statement: [Salt Palace, siteSubsequentUse, Salt Palace Convention Center expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siteSubsequentUse Context triple: [Salt Palace, siteSubsequentUse, Salt Palace Convention Center expansion]
-
A.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
B.
currentSiteUse
Indicates how a site is presently being used or the function it currently serves.
-
C.
laterUsedBy
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
-
D.
successorUseOfSite
chosen
Indicates that one use or function of a site directly follows and replaces a previous use of that same site in time.
-
E.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
- 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_69bd4409b264819085ab855f3eb5381a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2375a4819098e16acb982c8fab |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.