Triple
T27083549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Yarrow |
E685968
|
entity |
| Predicate | typeOfTributary |
P112502
|
FINISHED |
| Object | small tributary stream |
—
|
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: small tributary stream | Statement: [Little Yarrow, typeOfTributary, small tributary stream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTributary Context triple: [Little Yarrow, typeOfTributary, small tributary stream]
-
A.
tributary
Indicates that one watercourse flows into and feeds another, contributing its water to a larger stream, river, or lake.
-
B.
tributarySystemOf
Indicates that one political entity is subordinate to another, providing tribute or services in exchange for protection, recognition, or limited autonomy within a hierarchical system.
-
C.
isHeadwaterTributaryOf
Indicates that one watercourse is a source or upstream tributary that feeds into another watercourse.
-
D.
tributaryRank
chosen
Indicates the relative hierarchical level or importance of a tributary within a river or drainage network.
-
E.
locatedOnTributaryOf
Indicates that one entity is situated along or on the banks of a tributary that flows into another specified water body.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 27, 2026, 8:36 a.m.