Triple
T824623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Scala |
E17826
|
entity |
| Predicate | destroyedAndRebuilt |
P11808
|
FINISHED |
| Object | after World War II bombing |
—
|
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: after World War II bombing | Statement: [La Scala, destroyedAndRebuilt, after World War II bombing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destroyedAndRebuilt Context triple: [La Scala, destroyedAndRebuilt, after World War II bombing]
-
A.
destroyedDuring
chosen
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
B.
rebuiltMultipleTimes
Indicates that the same entity has been reconstructed or restored on more than one separate occasion.
-
C.
rebuiltFor
Indicates that one entity has been reconstructed, renovated, or modified specifically to serve the needs, purposes, or use of another entity.
-
D.
rebuiltUnder
Indicates that an entity was reconstructed or restored while being subject to the authority, control, or governance of another entity.
-
E.
reconstructedAfter
Indicates that one entity has been rebuilt, restored, or reassembled following the occurrence or existence of another entity or event.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab7eb0a08190889463edb0e7bd59 |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa781e1081909df006f730296c53 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.