Triple
T661526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stade de France |
E11765
|
entity |
| Predicate | openedForPublic |
P18212
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Stade de France, openedForPublic, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForPublic Context triple: [Stade de France, openedForPublic, 1998]
-
A.
openedForUse
Indicates that something has been made accessible and available for its intended operation or use.
-
B.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
-
C.
opened
Indicates that one entity caused another entity (such as an object, container, or passage) to change from a closed or inaccessible state to an open or accessible state.
-
D.
openedForThroughService
Indicates that an entity has been made accessible or available specifically for use via a through-service connection or route, rather than as a standalone endpoint.
-
E.
openedForEvent
Indicates that a venue or location is made accessible and operational specifically for a particular event.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a4a0f405748190ba72a9cfe946a8ec |
completed | March 1, 2026, 8:26 p.m. |
Created at: March 1, 2026, 7:36 p.m.