Triple
T2760203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zuma Rock |
E61200
|
entity |
| Predicate | heightAboveSurroundings |
P42978
|
FINISHED |
| Object | approximately 300 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 300 metres | Statement: [Zuma Rock, heightAboveSurroundings, approximately 300 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightAboveSurroundings Context triple: [Zuma Rock, heightAboveSurroundings, approximately 300 metres]
-
A.
roofHeight
Indicates the vertical distance or elevation of a roof relative to a reference level or structure.
-
B.
architecturalHeight
Indicates the measured vertical extent of a structure based on its architectural design, typically from the lowest significant level to the highest architecturally integral point, excluding non-architectural elements like antennas or masts.
-
C.
heightWithPedestal
Indicates the total vertical measurement of an object including the height of its supporting pedestal.
-
D.
relativeHeightAboveCity
Indicates the vertical height of an entity measured above the reference elevation level of a specified city.
-
E.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
- F. None of above. chosen
Provenance (4 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_69ab4b7bab6c8190a5c2efef19a8ef34 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfc5e1c8190a5ac2c48d3eaeb0a |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddcc348081908b5f760899389d4f |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 9:57 p.m.