Triple
T21751303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Rock, Edinburgh |
E536919
|
entity |
| Predicate | relativeHeightAboveSurroundings |
P42978
|
FINISHED |
| Object | about 80 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 80 metres | Statement: [Castle Rock, Edinburgh, relativeHeightAboveSurroundings, about 80 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeHeightAboveSurroundings Context triple: [Castle Rock, Edinburgh, relativeHeightAboveSurroundings, about 80 metres]
-
A.
heightAboveSurroundings
chosen
Indicates that an entity’s vertical position or elevation is higher than that of its immediate surrounding area.
-
B.
relativeHeightAboveCity
Indicates the vertical height of an entity measured above the reference elevation level of a specified city.
-
C.
heightAboveGround
Indicates the vertical distance of an entity measured from the ground surface directly beneath it.
-
D.
hasTypicalElevationRelativeTo
Indicates the usual height or altitude of one entity in comparison to a referenced baseline or other entity.
-
E.
elevationRelativeToWalls
Indicates the vertical position of an entity in relation to the height or level of surrounding walls.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8a6d4881908cc69e7247cce3a5 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.