Triple
T15179630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Coolum National Park |
E362705
|
entity |
| Predicate | summitTrackSurface |
P115885
|
FINISHED |
| Object | rocky |
—
|
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: rocky | Statement: [Mount Coolum National Park, summitTrackSurface, rocky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitTrackSurface Context triple: [Mount Coolum National Park, summitTrackSurface, rocky]
-
A.
hasTrackSurface
chosen
Indicates that an entity (such as a track) possesses or is characterized by a particular type of surface.
-
B.
summitShape
Indicates the geometric form or contour that characterizes the topmost point or summit of an object or landform.
-
C.
summitView
Indicates a vantage point or perspective that is obtained from the top or highest point of something, such as a mountain or structure.
-
D.
summitMaterial
Indicates that the material specified is what composes or covers the summit (top) of an object or geographic feature.
-
E.
summitDepth
Indicates the vertical distance from a summit’s highest point down to a specified reference level, such as a base or 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00664caac81909bee1268264769f8 |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.