Triple
T15401517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Highway |
E368327
|
entity |
| Predicate | formsPrimaryRouteBetween |
P69345
|
FINISHED |
| Object | Canberra and Sydney |
—
|
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: Canberra and Sydney | Statement: [Federal Highway, formsPrimaryRouteBetween, Canberra and Sydney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsPrimaryRouteBetween Context triple: [Federal Highway, formsPrimaryRouteBetween, Canberra and Sydney]
-
A.
formsPrimaryLinkBetween
chosen
Indicates that one entity serves as the main or most important connection or linkage between two other entities.
-
B.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
C.
formsKeyRouteTo
Indicates that something serves as a primary or essential pathway or connection leading to another thing.
-
D.
parallelRoute
Indicates that one route runs alongside and in the same general direction as another route without intersecting it.
-
E.
significantlyShortensRouteBetween
Indicates that one entity provides a connection between two others that makes the path or travel distance between them substantially shorter than alternative routes.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8ea0ac8190a5c68b1951ad3db1 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.