Triple
T2297115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morges River |
E51642
|
entity |
| Predicate | hasMouthCoordinate |
P18935
|
FINISHED |
| Object | near 46.51 N, 6.49 E |
—
|
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: near 46.51 N, 6.49 E | Statement: [Morges River, hasMouthCoordinate, near 46.51 N, 6.49 E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMouthCoordinate Context triple: [Morges River, hasMouthCoordinate, near 46.51 N, 6.49 E]
-
A.
hasPortNearMouth
Indicates that an entity possesses a port or opening located close to its mouth region.
-
B.
mouthNear
chosen
Indicates that one entity’s mouth is positioned close to another entity or object in space.
-
C.
hasMouthElevationApprox
Indicates an approximate vertical height or elevation value associated with the mouth of something (such as a feature, opening, or structure).
-
D.
mouthOf
Indicates the location where one entity (typically a river or similar feature) empties into or opens out into another, larger body or feature.
-
E.
mouth
Indicates that one entity is the mouth (oral opening) of another entity, typically serving as the location for ingestion, speech, or related functions.
- 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_69a88b0a9f248190bcff941463d8f65a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcd0e42248190ada33b84d75caa64 |
completed | March 7, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69abc589295c819092989820c2b4e9d8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.