Triple
T20907526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ploučnice River |
E514841
|
entity |
| Predicate | elevationOfMouth |
P35457
|
FINISHED |
| Object | approximately 120 m above sea level |
—
|
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 120 m above sea level | Statement: [Ploučnice River, elevationOfMouth, approximately 120 m above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationOfMouth Context triple: [Ploučnice River, elevationOfMouth, approximately 120 m above sea level]
-
A.
hasMouthElevationApprox
chosen
Indicates an approximate vertical height or elevation value associated with the mouth of something (such as a feature, opening, or structure).
-
B.
mouthDirection
Indicates the orientation or facing direction of a mouth relative to a reference frame or another object.
-
C.
hasMouthWidth
Indicates the measured horizontal extent or size of an entity’s mouth.
-
D.
mouth
Indicates that one entity is the mouth (oral opening) of another entity, typically serving as the location for ingestion, speech, or related functions.
-
E.
mouthNear
Indicates that one entity’s mouth is positioned close to another entity or object in space.
- 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e900ee7881909ab1046b40dca486 |
completed | April 21, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:47 p.m.