Triple
T37608429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucifron |
E935717
|
entity |
| Predicate | primaryDamageSchool |
P206003
|
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: [Lucifron, primaryDamageSchool, Fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDamageSchool Context triple: [Lucifron, primaryDamageSchool, Fire]
-
A.
primaryDamageType
Indicates the main kind of harm or injury that an action, event, or object is responsible for causing.
-
B.
secondaryDamageSchool
Indicates that a school experiences indirect or collateral damage as a consequence of another primary damaging event.
-
C.
damageClass
Indicates the type or category of damage associated with an action, event, or interaction between entities.
-
D.
damageBasis
Indicates the underlying reason, cause, or basis on which damage is determined or assessed in a given context.
-
E.
secondaryDamageType
Indicates the type of additional or follow-up damage that occurs as a consequence of a primary damaging event or effect.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.