Triple
T533686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tasmania |
E12278
|
entity |
| Predicate | hasHighestPointElevation |
P210
|
FINISHED |
| Object | 1617 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: 1617 metres | Statement: [Tasmania, hasHighestPointElevation, 1617 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestPointElevation Context triple: [Tasmania, hasHighestPointElevation, 1617 metres]
-
A.
highestPoint
chosen
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
C.
highestPointRegion
Indicates that one location is the highest point within a specified region.
-
D.
highestPeakClimbed
Indicates the tallest mountain or peak that an entity has successfully climbed.
-
E.
topographicProminence
Indicates the height of a peak’s summit relative to the lowest contour line encircling it and no higher summit, expressing how much it stands out from surrounding terrain.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b3e49081909810fa417b31306f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.