Triple
T325053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kings River |
E6495
|
entity |
| Predicate | hasFloodControlFunction |
P7637
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kings River, hasFloodControlFunction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloodControlFunction Context triple: [Kings River, hasFloodControlFunction, yes]
-
A.
hasFloodProtectionProject
chosen
Indicates that a flood protection project exists or is implemented for the referenced entity.
-
B.
flowControl
Indicates a relationship where one entity regulates, directs, or manages the rate or sequence of another entity’s operations or movement.
-
C.
hasCheckAndBalanceFunction
Indicates that one entity performs a checking or limiting role on another entity’s powers, providing oversight and balance within a system.
-
D.
fareControl
Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
-
E.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1a37c08190b1380f6bf8513a37 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e949364c8190bc2351f5413f5057 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.