Triple
T23158055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Weare Village (submerged by Everett Dam) |
E578499
|
entity |
| Predicate | typeOfLoss |
P43002
|
FINISHED |
| Object | inundation due to reservoir creation |
—
|
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: inundation due to reservoir creation | Statement: [East Weare Village (submerged by Everett Dam), typeOfLoss, inundation due to reservoir creation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLoss Context triple: [East Weare Village (submerged by Everett Dam), typeOfLoss, inundation due to reservoir creation]
-
A.
lossType
chosen
Indicates the specific category or nature of a loss associated with an entity or event.
-
B.
causedLossOf
Indicates that one entity brought about or was responsible for another entity experiencing a loss.
-
C.
significantLoss
Indicates that an entity has experienced a major or substantial decrease in value, quantity, or status beyond a normal or minor loss.
-
D.
regionOfLoss
Indicates the anatomical or spatial area where a loss, damage, or deficit occurs or is localized.
-
E.
liabilityType
Indicates the specific category or nature of liability associated with an entity, obligation, or financial exposure.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efeddd48190b6d03d2146583dcc |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.