Triple
T21661162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Lyndon B. Johnson |
E534597
|
entity |
| Predicate | primaryUses |
P77624
|
FINISHED |
| Object | hydroelectric power generation |
—
|
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: hydroelectric power generation | Statement: [Lake Lyndon B. Johnson, primaryUses, hydroelectric power generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUses Context triple: [Lake Lyndon B. Johnson, primaryUses, hydroelectric power generation]
-
A.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
B.
primaryHumanUse
chosen
Indicates the main way humans typically use, interact with, or benefit from the referenced entity.
-
C.
primaryUseArea
Indicates the main functional area or domain in which an entity is primarily used or applied.
-
D.
primaryUseStart
Indicates the point in time or event at which the primary use or main function of something begins.
-
E.
primaryCurrentUse
Indicates the main way something is currently being used or its principal present function.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef6c07bcb88190a9864672c20325ff |
completed | April 27, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:36 p.m.