Triple
T5226459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intuit Dome |
E117999
|
entity |
| Predicate | futureFunction |
P42365
|
FINISHED |
| Object | multi-purpose indoor arena |
—
|
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: multi-purpose indoor arena | Statement: [Intuit Dome, futureFunction, multi-purpose indoor arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureFunction Context triple: [Intuit Dome, futureFunction, multi-purpose indoor arena]
-
A.
laterFunction
Indicates that one function or event occurs after another in time.
-
B.
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.
-
C.
possibleFunction
Indicates that an entity may serve, or is capable of serving, a particular function or role, without asserting that it actually does so.
-
D.
associatedFunction
Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
-
E.
assignedFunction
Indicates that a specific role, duty, or function has been formally allocated to an entity.
- 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.