Triple
T28736426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odeon (concert hall) |
E730813
|
entity |
| Predicate | interiorStatusAfterWar |
P181419
|
FINISHED |
| Object | largely destroyed |
—
|
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: largely destroyed | Statement: [Odeon (concert hall), interiorStatusAfterWar, largely destroyed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interiorStatusAfterWar Context triple: [Odeon (concert hall), interiorStatusAfterWar, largely destroyed]
-
A.
exteriorStatusAfterWWII
Indicates the condition or classification of an entity’s exterior following the end of World War II.
-
B.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
C.
usedAfterWar
Indicates that an entity came into use only after a specific war or conflict had ended.
-
D.
statusDuringWar
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
E.
statusBeforeWar
Indicates the condition or situation of an entity as it existed prior to the onset of a specified war.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69f77648979c8190b6cdbb835ab8987c |
completed | May 3, 2026, 4:22 p.m. |
Created at: April 28, 2026, 6 a.m.