Triple
T3375507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New England Highway |
E71057
|
entity |
| Predicate | followsRouteNumber |
P1864
|
FINISHED |
| Object | A15 in New South Wales |
—
|
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: A15 in New South Wales | Statement: [New England Highway, followsRouteNumber, A15 in New South Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsRouteNumber Context triple: [New England Highway, followsRouteNumber, A15 in New South Wales]
-
A.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
B.
routeNumber
chosen
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
-
C.
formerRouteNumber
Indicates that an entity previously had a specific route number before being renumbered, discontinued, or otherwise changed.
-
D.
isNumberedRouteIn
Indicates that a numbered route (such as a highway or road with an assigned number) is located within or passes through a specified geographic or administrative area.
-
E.
routeNumberFormat
Indicates how the identifying number or code for a route is structured or formatted.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2e5fc6c81909ff582611751096d |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.