Triple
T23947208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pillow Rock |
E602945
|
entity |
| Predicate | riverSectionClass |
P17791
|
FINISHED |
| Object | Class V |
—
|
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: Class V | Statement: [Pillow Rock, riverSectionClass, Class V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverSectionClass Context triple: [Pillow Rock, riverSectionClass, Class V]
-
A.
watercourseSectionOf
Indicates that a watercourse segment forms a constituent part of a larger watercourse.
-
B.
downstreamRiverSection
Indicates that one river section is located downstream from, and receives flow from, another river section.
-
C.
waterwayClass
chosen
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
D.
riverFeatureType
Indicates the specific kind or category of physical or functional feature associated with a river (e.g., source, mouth, tributary, channel segment).
-
E.
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.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02ee0288190b58fd71b9cc65964 |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:17 p.m.