Triple
T4491097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nickajack Dam |
E107373
|
entity |
| Predicate | helpsControl |
P30853
|
FINISHED |
| Object | flooding on the Tennessee River |
—
|
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: flooding on the Tennessee River | Statement: [Nickajack Dam, helpsControl, flooding on the Tennessee River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpsControl Context triple: [Nickajack Dam, helpsControl, flooding on the Tennessee River]
-
A.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
B.
canControl
chosen
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
C.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
D.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
-
E.
controlMethods
Indicates the methods or techniques used by one entity to direct, regulate, or influence the behavior, operation, or state of another entity.
- 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_69bd43f84f788190a1383579c4a595be |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd556e69f88190b9c16afc2afcdbef |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd5213e3d0819094b026989e686f01 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 12:59 p.m.