Triple
T6041266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aoraki / Mount Cook |
E134549
|
entity |
| Predicate | hadHeightReducedBy |
P68330
|
FINISHED |
| Object | approximately 10 metres in 1991 rockfall |
—
|
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 10 metres in 1991 rockfall | Statement: [Aoraki / Mount Cook, hadHeightReducedBy, approximately 10 metres in 1991 rockfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadHeightReducedBy Context triple: [Aoraki / Mount Cook, hadHeightReducedBy, approximately 10 metres in 1991 rockfall]
-
A.
dropHeight
Indicates the vertical distance from which an object is released or allowed to fall.
-
B.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
C.
reducedCapacity
Indicates that an entity is functioning with less than its normal or full capacity, ability, or effectiveness.
-
D.
cutDown
Indicates that an agent causes something standing or elevated (such as a tree or structure) to fall or be reduced by cutting.
-
E.
heightClaim
Indicates that one entity asserts or reports a specific height for another entity (or itself).
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056d11370819096ac35349bd91f4e |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049eb52a08190ac10fd703735f5aa |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:08 p.m.