Triple
T257728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacandaga River |
E5471
|
entity |
| Predicate | purposeOfRegulation |
P79
|
FINISHED |
| Object | flood control |
—
|
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 control | Statement: [Sacandaga River, purposeOfRegulation, flood control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfRegulation Context triple: [Sacandaga River, purposeOfRegulation, flood control]
-
A.
regulatesUse
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
-
B.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
C.
regulatoryDomain
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
-
D.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
E.
legalBasis
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25f921c2881908821ca2c03815eae |
completed | Feb. 28, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69a25b6b3ea88190bbd858999e42efae |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.