Triple
T26395171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leaning Tower of Pisa |
E663526
|
entity |
| Predicate | closedForStabilization |
P116566
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Leaning Tower of Pisa, closedForStabilization, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedForStabilization Context triple: [Leaning Tower of Pisa, closedForStabilization, 1990]
-
A.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
B.
closedDuring
Indicates that an entity is not open or available for use during a specified time period or under certain conditions.
-
C.
closedBy
Indicates that one entity performs the action of closing, finishing, or terminating another entity (such as a task, issue, or process).
-
D.
closedForReconstructionTo
chosen
Indicates that access or use of something is prohibited for a party because it is undergoing reconstruction.
-
E.
closedBefore
Indicates that one entity was closed at an earlier time than another 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 26, 2026, 11:28 p.m.