Triple
T15859663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Moose River |
E384549
|
entity |
| Predicate | watercourseSectionOf |
P120790
|
FINISHED |
| Object | Moose River waterway |
—
|
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: Moose River waterway | Statement: [Middle Moose River, watercourseSectionOf, Moose River waterway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourseSectionOf Context triple: [Middle Moose River, watercourseSectionOf, Moose River waterway]
-
A.
watercourseFor
Indicates that one entity serves as the watercourse (such as a river or channel) associated with, carrying, or draining another entity.
-
B.
downstreamRiverSection
Indicates that one river section is located downstream from, and receives flow from, another river section.
-
C.
watercourseFeature
Indicates that a feature is a physical characteristic or component associated with a watercourse (such as a river, stream, or canal).
-
D.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
E.
watercourseId
Indicates the identifier that uniquely associates an entity with a specific watercourse (such as a river, stream, or canal).
- F. None of above. chosen
Provenance (4 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:50 a.m.