Triple
T27255012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denison Dam Power Plant |
E687588
|
entity |
| Predicate | locatedNearState |
P96807
|
FINISHED |
| Object | Texas |
—
|
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: Texas | Statement: [Denison Dam Power Plant, locatedNearState, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedNearState Context triple: [Denison Dam Power Plant, locatedNearState, Texas]
-
A.
nearbyState
Indicates that one state is geographically adjacent to or in close proximity to another state.
-
B.
nearbyStateOrProvince
Indicates that one state or province is geographically close to, but not necessarily directly bordering, another state or province.
-
C.
nearestStateOrTerritory
Indicates that one location is the closest state or territory to another location, typically in terms of geographic distance.
-
D.
locatedInStateOrRegion
chosen
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
E.
nearByCityState
Indicates that a city is geographically close to or within the same general area as a specified state.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: April 27, 2026, 10:48 a.m.