Triple
T30587841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fraser Lake outlet |
E778565
|
entity |
| Predicate | waterbodyRole |
P13535
|
FINISHED |
| Object | lake outlet |
—
|
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: lake outlet | Statement: [Fraser Lake outlet, waterbodyRole, lake outlet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterbodyRole Context triple: [Fraser Lake outlet, waterbodyRole, lake outlet]
-
A.
waterbodyType
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
-
B.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
C.
waterbodyID
Indicates a unique identifier that links an entity to a specific body of water.
-
D.
formsBodyOfWater
Indicates that one entity constitutes or creates the physical substance or structure that makes up a particular body of water.
-
E.
hasWaterwayRole
chosen
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 29, 2026, 8:24 p.m.