Triple
T15082636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gillespie Dam |
E360187
|
entity |
| Predicate | yearOfPartialFailure |
P117239
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Gillespie Dam, yearOfPartialFailure, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfPartialFailure Context triple: [Gillespie Dam, yearOfPartialFailure, 1993]
-
A.
reasonForPartialSuccess
Indicates the explanation or cause for why an outcome was only partially successful rather than fully achieved.
-
B.
hasPartiallyLostUseOf
Indicates that an entity has experienced a reduction, but not a complete loss, in the functional use of another entity.
-
C.
partiallyDismantledInYear
Indicates that an entity was only partly taken apart, deconstructed, or removed in the specified year.
-
D.
hasPartInYear
Indicates that something includes or contains a specific part, component, or segment that is associated with a particular year.
-
E.
partiallyDestroyed
Indicates that an entity has been damaged or ruined to a significant extent but not completely destroyed.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0027450a48190a84588b6aaf84ebf |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:03 a.m.