Triple
T27255046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denison Dam Power Plant |
E687588
|
entity |
| Predicate | usesHeadFrom |
P162529
|
FINISHED |
| Object | Denison Dam |
—
|
NE NERFINISHED |
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: Denison Dam | Statement: [Denison Dam Power Plant, usesHeadFrom, Denison Dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHeadFrom Context triple: [Denison Dam Power Plant, usesHeadFrom, Denison Dam]
-
A.
electHeadBy
Indicates that a group or body selects and appoints a person to serve as its head or leader through an election process.
-
B.
tookHeadOf
Indicates that one entity removed or claimed the head (literal or symbolic) of another entity.
-
C.
hasHeadOf
Indicates that one entity serves as the leader, chief, or person in charge of another entity (such as an organization, group, or department).
-
D.
headGivesRiseTo
Indicates that one entity (the head) is the source or origin from which another entity arises, develops, or is produced.
-
E.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f625402d808190be8279d895d2b27f |
completed | May 2, 2026, 4:24 p.m. |
Created at: April 27, 2026, 10:48 a.m.