Triple
T32112443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Routeburn River |
E820151
|
entity |
| Predicate | hasTrackAlong |
P120265
|
FINISHED |
| Object | Routeburn Track |
—
|
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: Routeburn Track | Statement: [Routeburn River, hasTrackAlong, Routeburn Track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrackAlong Context triple: [Routeburn River, hasTrackAlong, Routeburn Track]
-
A.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
B.
hasTrackControl
Indicates that one entity has authority or capability to manage, direct, or regulate the operation or behavior of another entity’s track or tracking process.
-
C.
hasTrackSection
Indicates that an entity includes, is composed of, or is associated with a specific section or segment of a track.
-
D.
hasAlongRoute
chosen
Indicates that one entity lies on or is situated along the path, course, or route taken by another entity.
-
E.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 1, 2026, 12:27 a.m.