Triple
T6872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee Valley Authority |
E136
|
entity |
| Predicate | manages |
P86
|
FINISHED |
| Object | flood risk in the Tennessee Valley |
—
|
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: flood risk in the Tennessee Valley | Statement: [Tennessee Valley Authority, manages, flood risk in the Tennessee Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manages Context triple: [Tennessee Valley Authority, manages, flood risk in the Tennessee Valley]
-
A.
organizes
Indicates that one entity arranges, coordinates, or structures activities, items, or people into an ordered or planned form for a particular purpose.
-
B.
administeredBy
chosen
Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
-
C.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
D.
governance
Indicates the relationship in which one entity exercises authority, control, or decision-making power over the policies, actions, or direction of another entity or system.
-
E.
operatesBy
Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
- 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_69a23bb612708190b09f25385e4b63d1 |
completed | Feb. 28, 2026, 12:49 a.m. |
| NER | Named-entity recognition | batch_69a241a55ac081909e95b71c97db8140 |
completed | Feb. 28, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69a23fe1cf38819080ea56c40bf2632e |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 12:54 a.m.