Triple
T3151095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SoFi Stadium |
E65877
|
entity |
| Predicate | futureEventRole |
P21890
|
FINISHED |
| Object | Olympic ceremonies venue |
—
|
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: Olympic ceremonies venue | Statement: [SoFi Stadium, futureEventRole, Olympic ceremonies venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureEventRole Context triple: [SoFi Stadium, futureEventRole, Olympic ceremonies venue]
-
A.
eventRole
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
B.
plannedRole
chosen
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
C.
significantEventRole
Indicates that an entity plays an important or defining role in a particular significant event.
-
D.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
E.
laterPrimaryRole
Indicates that an entity assumes a specified primary role at a later time than another role or state in a sequence.
- 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_69ad8584485081909ed529e890cadc4a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5c145248190843ff3b1701074a1 |
completed | March 8, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfa3d9081908425aa636bb9b897 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.