Triple
T18391607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hales Bar Dam |
E449741
|
entity |
| Predicate | hadIssues |
P90681
|
FINISHED |
| Object | chronic leakage |
—
|
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: chronic leakage | Statement: [Hales Bar Dam, hadIssues, chronic leakage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadIssues Context triple: [Hales Bar Dam, hadIssues, chronic leakage]
-
A.
hadIssue
chosen
Indicates that an entity experienced, encountered, or was affected by a particular problem, defect, or difficulty.
-
B.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
C.
hasBackIssues
Indicates that an entity experiences or possesses problems, conditions, or complications related to its back.
-
D.
hadKeyIssue
Indicates that an entity experienced a primary or critical problem related to a key aspect, factor, or component.
-
E.
hasRecentIssue
Indicates that an entity is associated with an issue or problem that has occurred within a recent or specified time frame.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e518422e488190bd06fad72efa1641 |
completed | April 19, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.