Triple
T16710226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fucha River headwaters |
E406087
|
entity |
| Predicate | watercourseOriginType |
P12617
|
FINISHED |
| Object | mountain streams |
—
|
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: mountain streams | Statement: [Fucha River headwaters, watercourseOriginType, mountain streams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourseOriginType Context triple: [Fucha River headwaters, watercourseOriginType, mountain streams]
-
A.
sourceOfWatercourse
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
-
B.
majorRiverSource
Indicates that one entity is the primary originating source or headwaters location of a major river.
-
C.
hasHydronymOrigin
Indicates that something derives its name from a body of water or hydrological feature.
-
D.
waterOrigin
chosen
Indicates the source or starting location from which the water originates or is supplied.
-
E.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3865186b48190bb45a761f5cf1a83 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.