Triple
T8782807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moerenuma Park |
E208772
|
entity |
| Predicate | MountMoereHeight |
P14507
|
FINISHED |
| Object | approximately 62 meters |
—
|
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 62 meters | Statement: [Moerenuma Park, MountMoereHeight, approximately 62 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MountMoereHeight Context triple: [Moerenuma Park, MountMoereHeight, approximately 62 meters]
-
A.
summitElevation
chosen
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
B.
isRockySummitOf
Indicates that one entity is the rocky summit or peak portion of another, typically higher-level, geographic feature.
-
C.
territorialPeak
Indicates the highest geographical point located within the territory or jurisdiction of a given entity.
-
D.
parentMountain
Indicates that one mountain is considered the larger or primary "parent" from which another, related "child" mountain is derived or associated.
-
E.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
- 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_69ca835fbee88190bf625939bac48d7f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f7155b081908891e84b704f0ebf |
completed | March 31, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:42 p.m.