Triple
T409305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orinoco Basin headwaters |
E9451
|
entity |
| Predicate | feeds |
P9008
|
FINISHED |
| Object | Orinoco main stem |
—
|
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: Orinoco main stem | Statement: [Orinoco Basin headwaters, feeds, Orinoco main stem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feeds Context triple: [Orinoco Basin headwaters, feeds, Orinoco main stem]
-
A.
feedSystem
chosen
Indicates that one entity supplies or provides input, resources, or data into another entity or system for its operation or processing.
-
B.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
C.
front
Indicates that one entity is located directly before or facing another entity along a primary viewing or movement direction.
-
D.
finds
Indicates that one entity discovers, locates, or comes upon another entity, often as the result of a search or encounter.
-
E.
feast
Indicates that an entity participates in or hosts a large, elaborate meal or celebration involving abundant food and communal dining.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ed31681c8190ac32334562fb17fd |
completed | Feb. 28, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69a2e9737694819080fde9adcc1aa4d4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.