Triple
T439046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St James's Palace, London |
E10073
|
entity |
| Predicate | fireEvent |
P13164
|
FINISHED |
| Object | damaging fire in 1809 |
—
|
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: damaging fire in 1809 | Statement: [St James's Palace, London, fireEvent, damaging fire in 1809]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireEvent Context triple: [St James's Palace, London, fireEvent, damaging fire in 1809]
-
A.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
B.
launchEvent
Indicates an event in which something is formally initiated, introduced, or set into operation.
-
C.
formationEvent
Indicates the event or process through which something comes into existence, is created, or is initially established.
-
D.
endUseEvent
Indicates an event marking the final or terminating use of something by an entity.
-
E.
triggerEventLocation
Indicates the location where a triggering event occurs or is initiated.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef283be881909444aaf257451747 |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddcf50c8190bfa0d1f8ee9f604a |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeb9e6b0819093863959a6e5730a |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.