Triple
T19064653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Head vicinity headlands |
E466621
|
entity |
| Predicate | hasWalkingTracks |
P74037
|
FINISHED |
| Object | summit tracks |
—
|
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: summit tracks | Statement: [North Head vicinity headlands, hasWalkingTracks, summit tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWalkingTracks Context triple: [North Head vicinity headlands, hasWalkingTracks, summit tracks]
-
A.
hasWalkingRouteType
chosen
Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
-
B.
hasWalkingPathAround
Indicates that one entity has a walking path that encircles or runs around another entity.
-
C.
walks
Indicates that an entity moves on foot from one place to another, typically at a regular, moderate pace.
-
D.
isHikingTrail
Indicates that a path or route is designated and used specifically for hiking activities.
-
E.
hasWalkingRouteConnection
Indicates that there is a walkable path or route directly connecting two locations.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19799d8819099d0b848771ae425 |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.