Triple
T18583562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yana Bay |
E454180
|
entity |
| Predicate | receivesMouthOf |
P99332
|
FINISHED |
| Object | Yana River |
—
|
NE NERFINISHED |
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: Yana River | Statement: [Yana Bay, receivesMouthOf, Yana River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesMouthOf Context triple: [Yana Bay, receivesMouthOf, Yana River]
-
A.
fromMouth
Indicates that something originates from or is emitted out of a mouth.
-
B.
mouthOf
Indicates the location where one entity (typically a river or similar feature) empties into or opens out into another, larger body or feature.
-
C.
containsMouthOf
chosen
Indicates that one entity geographically includes or encompasses the mouth (outflow point) of another entity, such as a river or stream.
-
D.
mouthpieceOf
Indicates that one entity serves as the spokesperson or public voice expressing the views or positions of another entity.
-
E.
hasTypeOfMouth
Indicates that an entity possesses a mouth characterized by a specific type or form.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543d200dc8190b8797d731f4e4865 |
completed | April 19, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.