Triple
T27465099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namdaemun |
E693155
|
entity |
| Predicate | sufferedFireDamage |
P124183
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Namdaemun, sufferedFireDamage, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufferedFireDamage Context triple: [Namdaemun, sufferedFireDamage, 2008]
-
A.
destroyedByFire
Indicates that something has been ruined, damaged, or rendered unusable as a direct result of a fire.
-
B.
partiallyDestroyedByFire
chosen
Indicates that an entity has been damaged to some extent, but not completely destroyed, as a result of a fire.
-
C.
sufferedDamageTo
Indicates that one entity has experienced harm, loss, or deterioration affecting another entity or one of its parts.
-
D.
consequenceOfFire
Indicates that something occurs as a result or outcome of a fire.
-
E.
sufferedDestructionOf
Indicates that one entity experienced damage, ruin, or loss as a result of the destruction of another entity.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62dfca4448190b324f605171a531a |
completed | May 2, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:51 p.m.