Triple
T7915090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flint River |
E183801
|
entity |
| Predicate | waterSourcePeriod |
P54962
|
FINISHED |
| Object | 2014–2015 (primary municipal source for Flint) |
—
|
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: 2014–2015 (primary municipal source for Flint) | Statement: [Flint River, waterSourcePeriod, 2014–2015 (primary municipal source for Flint)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterSourcePeriod Context triple: [Flint River, waterSourcePeriod, 2014–2015 (primary municipal source for Flint)]
-
A.
waterSourceAfter
Indicates that one water source occurs, appears, or is accessed after another in time or sequence.
-
B.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
C.
waterSourceContext
chosen
Indicates the contextual relationship between a water source and the conditions, setting, or circumstances under which it is used, accessed, or relevant.
-
D.
waterSourceDedicatedTo
Indicates that a particular water source is specifically allocated or reserved for a designated use, group, or purpose.
-
E.
waterSourceType
Indicates the kind or category of source from which water is obtained.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a759b548190af2e2aa0705d7051 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:05 p.m.