Triple
T17599722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyline Rotorua |
E428660
|
entity |
| Predicate | primaryTransportModeToAccess |
P70707
|
FINISHED |
| Object | road vehicles |
—
|
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: road vehicles | Statement: [Skyline Rotorua, primaryTransportModeToAccess, road vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTransportModeToAccess Context triple: [Skyline Rotorua, primaryTransportModeToAccess, road vehicles]
-
A.
usedTransportationMode
Indicates that an entity traveled or moved using a specified mode of transportation.
-
B.
transportModeImportant
Indicates that the mode of transport used is considered significant or plays an important role in the context of the relationship or action.
-
C.
hasPrimaryTransportationMode
chosen
Indicates the main or most frequently used mode of transportation associated with an entity.
-
D.
publicTransitMode
Indicates the type of public transportation (e.g., bus, train, subway) used or associated with a given trip or segment.
-
E.
transportModeAccess
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c4812d48190bf8e899fa8f7fbe4 |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.