Triple
T11700206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ribemont |
E278102
|
entity |
| Predicate | hasElevationMaximum |
P99098
|
FINISHED |
| Object | 139 metres |
—
|
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: 139 metres | Statement: [Ribemont, hasElevationMaximum, 139 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElevationMaximum Context triple: [Ribemont, hasElevationMaximum, 139 metres]
-
A.
elevationRangeUpperBound
Indicates the maximum elevation value that bounds the upper limit of an elevation range for something.
-
B.
peakElevationMetres
chosen
Indicates the maximum height of an entity above sea level, measured in metres.
-
C.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
D.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
E.
highestPassApproxElevation
Indicates the approximate elevation of the highest pass along a given route or within a specified 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49a025881909377c81d3debf465 |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.