Triple
T36030966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghost Gum Walk |
E1042255
|
entity |
| Predicate | isShortWalkFrom |
P53938
|
FINISHED |
| Object | Ormiston Gorge campground |
—
|
NE NERFINISHED |
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: Ormiston Gorge campground | Statement: [Ghost Gum Walk, isShortWalkFrom, Ormiston Gorge campground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isShortWalkFrom Context triple: [Ghost Gum Walk, isShortWalkFrom, Ormiston Gorge campground]
-
A.
hasNearbyWalkingRoutes
Indicates that there are walkable paths or routes located close to the referenced entity.
-
B.
hasTransportationProximityTo
Indicates that one entity is located near or conveniently accessible to another entity in terms of transportation options or routes.
-
C.
hasApproximateWalkingTimeTo
chosen
Indicates that there is an estimated or approximate amount of time it takes to walk from one entity to another.
-
D.
proximityToLandmark
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
-
E.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ad177a5081908793d30c24b68af5 |
completed | May 3, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.