Triple
T36160458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toce River |
E1045859
|
entity |
| Predicate | mouthCoordinates |
P100750
|
FINISHED |
| Object | approximately 45.93°N 8.53°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: approximately 45.93°N 8.53°E | Statement: [Toce River, mouthCoordinates, approximately 45.93°N 8.53°E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mouthCoordinates Context triple: [Toce River, mouthCoordinates, approximately 45.93°N 8.53°E]
-
A.
mouthDirection
Indicates the orientation or facing direction of a mouth relative to a reference frame or another object.
-
B.
hasMouthCoordinates
chosen
Indicates that specific spatial coordinates are associated with the location of an entity's mouth.
-
C.
mouthNear
Indicates that one entity’s mouth is positioned close to another entity or object in space.
-
D.
mouthFormation
Indicates the specific shape or configuration the mouth takes while producing a sound or expression.
-
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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.