Triple
T20948535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devecser |
E515914
|
entity |
| Predicate | hasReconstructionAfterDisaster |
P28319
|
FINISHED |
| Object | post-2010 rebuilding program |
—
|
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: post-2010 rebuilding program | Statement: [Devecser, hasReconstructionAfterDisaster, post-2010 rebuilding program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReconstructionAfterDisaster Context triple: [Devecser, hasReconstructionAfterDisaster, post-2010 rebuilding program]
-
A.
hasReconstructionPlan
Indicates that there exists a defined plan or strategy for rebuilding, restoring, or reconstructing a given entity or system.
-
B.
reconstructedAfter
Indicates that one entity has been rebuilt, restored, or reassembled following the occurrence or existence of another entity or event.
-
C.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
D.
wasReconstructed
Indicates that something previously existing was rebuilt or restored after damage, destruction, or alteration.
-
E.
hasReconstructionWork
chosen
Indicates that an entity is undergoing, has undergone, or is associated with reconstruction or restoration work.
- 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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fadab7708190bb3a10bdd3f32d90 |
completed | April 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 1:10 p.m.