Triple
T5226447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intuit Dome |
E117999
|
entity |
| Predicate | futureStatus |
P42365
|
FINISHED |
| Object | future home venue of the Los Angeles Clippers |
—
|
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: future home venue of the Los Angeles Clippers | Statement: [Intuit Dome, futureStatus, future home venue of the Los Angeles Clippers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureStatus Context triple: [Intuit Dome, futureStatus, future home venue of the Los Angeles Clippers]
-
A.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
B.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
C.
fareStatus
Indicates the current condition or classification of a fare within a pricing or ticketing context (e.g., available, restricted, or expired).
-
D.
futureComponentOf
chosen
Indicates that one entity is expected or planned to become a component or part of another entity at some point in the future.
-
E.
peakStatus
Indicates the condition or phase of something at its highest or most intense point in its progression or lifecycle.
- 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adc9be081909903b9f844c3d146 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.