Triple
T9389303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serein |
E225982
|
entity |
| Predicate | tributaryDirectionRelativeToYonne |
P75396
|
FINISHED |
| Object | right |
—
|
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: right | Statement: [Serein, tributaryDirectionRelativeToYonne, right]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tributaryDirectionRelativeToYonne Context triple: [Serein, tributaryDirectionRelativeToYonne, right]
-
A.
waterwayDirection
chosen
Indicates the directional flow or orientation of a waterway relative to a reference point or path.
-
B.
isMajorWatercourseOf
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
-
C.
distributaryOf
Indicates that one watercourse branches off from a main river or stream and carries its water away, rather than feeding into it.
-
D.
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.
-
E.
upstreamRiver
Indicates that one river is located or flows in an upstream direction relative to another river within the same watercourse system.
- 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_69ca842f7e3481908bf5bcf52e032dbd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50d83c188190925c389dff1341b0 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.