Triple
T661567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stade de France |
E11765
|
entity |
| Predicate | plannedEvent |
P11255
|
FINISHED |
| Object | 2024 Summer Olympics ceremonies and events |
—
|
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: 2024 Summer Olympics ceremonies and events | Statement: [Stade de France, plannedEvent, 2024 Summer Olympics ceremonies and events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedEvent Context triple: [Stade de France, plannedEvent, 2024 Summer Olympics ceremonies and events]
-
A.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
B.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
-
C.
announcementOccasion
Indicates the specific event, context, or circumstance on the basis of which an announcement is made.
-
D.
agendaItem
Indicates that something is an item or entry on a planned agenda or schedule of topics to be addressed.
-
E.
planned
chosen
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0f55f7481909e052a25bd12d455 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d1406ec8190abf546549264c85d |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.