Triple
T20548591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney–Perth corridor (via Adelaide) |
E504538
|
entity |
| Predicate | routeQualifier |
P65442
|
FINISHED |
| Object | via Adelaide |
—
|
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: via Adelaide | Statement: [Sydney–Perth corridor (via Adelaide), routeQualifier, via Adelaide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeQualifier Context triple: [Sydney–Perth corridor (via Adelaide), routeQualifier, via Adelaide]
-
A.
routeMayInclude
chosen
Indicates that a given route can optionally pass through, contain, or involve a specified segment, location, or element as part of its path.
-
B.
routeSpecialization
Indicates that one route is a specialized or more specific variant of another, more general route.
-
C.
routeRole
Indicates the specific functional role or purpose that an entity has within a particular route or path.
-
D.
routeSymbol
Indicates that a particular symbol or code is used to represent or identify a specific route.
-
E.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5d56060819090f0e2f2f9957982 |
completed | April 20, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:38 a.m.