Triple
T5670445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auckland Region |
E124960
|
entity |
| Predicate | hasMotorwayNetwork |
P385
|
FINISHED |
| Object | Auckland motorway network |
—
|
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: Auckland motorway network | Statement: [Auckland Region, hasMotorwayNetwork, Auckland motorway network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMotorwayNetwork Context triple: [Auckland Region, hasMotorwayNetwork, Auckland motorway network]
-
A.
motorwayServedBy
Indicates that a motorway is connected to or accessed by a particular service facility, route, or transport service.
-
B.
hasExpresswaySection
Indicates that an entity includes, contains, or is associated with a specific section or segment of an expressway.
-
C.
isOnOrbitalMotorway
Indicates that one entity (typically a route or segment) lies on or forms part of an orbital motorway that encircles a city or area.
-
D.
hasMajorHighway
chosen
Indicates that a location or area is served by or directly connected to a major highway route.
-
E.
hasSmartMotorwaySection
Indicates that a road or route includes at least one section designated and operated as a smart motorway.
- 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.