Triple
T4493620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Victoria Lookout |
E100637
|
entity |
| Predicate | hasWalkingTrackNetwork |
P20893
|
FINISHED |
| Object | Mount Victoria walking 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: Mount Victoria walking tracks | Statement: [Mount Victoria Lookout, hasWalkingTrackNetwork, Mount Victoria walking tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWalkingTrackNetwork Context triple: [Mount Victoria Lookout, hasWalkingTrackNetwork, Mount Victoria walking tracks]
-
A.
hasTrailNetwork
chosen
Indicates that an entity possesses or is associated with a system of interconnected trails or paths.
-
B.
hasNearbyTrail
Indicates that one entity is located close to or within a short distance of a trail.
-
C.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
-
D.
TrailLinkIs
Indicates that one trail segment is connected to or continues from another trail segment.
-
E.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
- 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5570ba0881908f5fb4f8d0730e64 |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd5213e3d0819094b026989e686f01 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1 p.m.