Triple
T9437756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Awash River |
E227557
|
entity |
| Predicate | doesNotReach |
P35927
|
FINISHED |
| Object | sea |
—
|
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: sea | Statement: [Awash River, doesNotReach, sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotReach Context triple: [Awash River, doesNotReach, sea]
-
A.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
B.
doesNotTry
Indicates that an entity makes no attempt to perform a particular action or engage in a specified activity.
-
C.
doesNotEnter
chosen
Indicates that one entity refrains from or fails to go into or cross the boundary of another entity or location.
-
D.
ultimatelyDoesNot
Indicates that, despite any preceding conditions or possibilities, the referenced entity or action does not in the end occur, hold, or get carried out.
-
E.
doesNotCover
Indicates that one entity fails to include, protect, or extend over another entity or area.
- 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7edff5e881909b72976e8909ba4b |
completed | April 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:50 p.m.