Triple
T16898330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frendo Spur |
E424367
|
entity |
| Predicate | heightGain |
P125114
|
FINISHED |
| Object | approximately 1200 m |
—
|
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 1200 m | Statement: [Frendo Spur, heightGain, approximately 1200 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightGain Context triple: [Frendo Spur, heightGain, approximately 1200 m]
-
A.
heightDescription
Indicates how tall an entity is, typically expressed in descriptive or qualitative terms rather than a precise measurement.
-
B.
heightInMetres
Indicates the height of an entity expressed as a measurement in metres.
-
C.
estimatedHeadHeightInMeters
Indicates the estimated vertical height of a person's head, measured in meters.
-
D.
heightAboveGround
Indicates the vertical distance of an entity measured from the ground surface directly beneath it.
-
E.
heightReference
Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8d98c308190bcc0adc7797d1f40 |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:29 a.m.