Triple
T21193895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Machrie Moor |
E522277
|
entity |
| Predicate | hasHighestStoneHeight |
P75035
|
FINISHED |
| Object | approximately 5.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: approximately 5.5 metres | Statement: [Machrie Moor, hasHighestStoneHeight, approximately 5.5 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestStoneHeight Context triple: [Machrie Moor, hasHighestStoneHeight, approximately 5.5 metres]
-
A.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
-
B.
hasHighestPeaksOver
Indicates that one entity possesses mountain peaks that are higher in elevation than those of another entity.
-
C.
hasHighestStructure
chosen
Indicates that an entity possesses the tallest or most elevated structural feature compared to all other relevant entities in a given context.
-
D.
maximumMoundHeight
Indicates the greatest allowable or observed height of a mound relative to a specified reference or context.
-
E.
hasHigherSummit
Indicates that one entity’s summit is higher in elevation than another entity’s summit.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73339aaa081909d9009c58c386422 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:08 p.m.