Triple
T13679914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fonserannes Locks |
E327971
|
entity |
| Predicate | elevationDifferenceBetweenEnds |
P6813
|
FINISHED |
| Object | about 21.5 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: about 21.5 metres | Statement: [Fonserannes Locks, elevationDifferenceBetweenEnds, about 21.5 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationDifferenceBetweenEnds Context triple: [Fonserannes Locks, elevationDifferenceBetweenEnds, about 21.5 metres]
-
A.
endElevation
Indicates the elevation or vertical position at which something finishes, terminates, or reaches its endpoint.
-
B.
elevationChange
chosen
Indicates a change in vertical position or altitude between two points or states.
-
C.
elevationGainRelativeToBase
Indicates the amount of elevation increase of something compared to a defined base level.
-
D.
elevationAtBase
Indicates the height or altitude measured at the base or lowest point of an object or feature relative to a reference level.
-
E.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66cbb088190907cb89dda8e4ebd |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.