Triple
T319024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notre-Dame Cathedral |
E7770
|
entity |
| Predicate | plannedReopening |
P10067
|
FINISHED |
| Object | 2024 |
—
|
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 | Statement: [Notre-Dame Cathedral, plannedReopening, 2024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedReopening Context triple: [Notre-Dame Cathedral, plannedReopening, 2024]
-
A.
reopeningDate
chosen
Indicates the date on which something that was previously closed is opened again for use or access.
-
B.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
C.
plannedFacility
Indicates that a facility is intended or scheduled to be built, established, or implemented in the future but does not yet exist or operate.
-
D.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
-
E.
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.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb7df63c8190b7cd1bcfdfd96187 |
completed | Feb. 28, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69a2e94513ec819089f5177f7a521e65 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.