Triple
T1288631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glenbrook Creek |
E27492
|
entity |
| Predicate | hasWatercourseRole |
P13535
|
FINISHED |
| Object | tributary of Lake Tahoe |
—
|
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: tributary of Lake Tahoe | Statement: [Glenbrook Creek, hasWatercourseRole, tributary of Lake Tahoe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWatercourseRole Context triple: [Glenbrook Creek, hasWatercourseRole, tributary of Lake Tahoe]
-
A.
hasWaterwayRole
chosen
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
-
B.
sourceOfWatercourse
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
-
C.
hydrologicallyConnectedTo
Indicates that two water bodies or hydrological features are linked such that water can flow or be transferred between them, directly or indirectly, through the hydrological system.
-
D.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
-
E.
watercourseName
Indicates the name assigned to a river, stream, or other flowing body of water in the relationship.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d38d7c81908941edda9cac5d6a |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.