Triple
T33571940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurobe Dam |
E859922
|
entity |
| Predicate | casualtiesDuringConstruction |
P72408
|
FINISHED |
| Object | over 100 workers |
—
|
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: over 100 workers | Statement: [Kurobe Dam, casualtiesDuringConstruction, over 100 workers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesDuringConstruction Context triple: [Kurobe Dam, casualtiesDuringConstruction, over 100 workers]
-
A.
demolitionCasualties
Indicates that an act of demolition resulted in injuries or deaths to people involved or nearby.
-
B.
constructionAccidentFatalities
chosen
Indicates that a construction-related accident resulted in one or more fatalities.
-
C.
primaryCasualtiesFrom
Indicates that an entity is the main source or cause of the casualties experienced by another entity.
-
D.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f74620dc819081b0aeb6490815eb |
completed | May 3, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.