Triple
T21016436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goetheanum |
E517688
|
entity |
| Predicate | firstBuildingDestroyedBy |
P81247
|
FINISHED |
| Object | fire |
—
|
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: fire | Statement: [Goetheanum, firstBuildingDestroyedBy, fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstBuildingDestroyedBy Context triple: [Goetheanum, firstBuildingDestroyedBy, fire]
-
A.
originalBuildingDestroyedBy
Indicates that the original building was destroyed as a result of the actions or effects of the specified agent or cause.
-
B.
secondBuildingDestroyedBy
Indicates that the second building in a specified context is the one that was destroyed by a particular agent or event.
-
C.
firstBuildingDestroyedByFire
chosen
Indicates that the first building in a given context was destroyed as a result of a fire.
-
D.
firstPalaceDestroyedBy
Indicates that the subject’s first palace was destroyed by the specified agent or cause.
-
E.
buildingsDestroyed
Indicates that one or more buildings have been damaged to the point of destruction as a result of some event or action.
- 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc5968c081909ae6407199858aba |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:54 p.m.