Triple
T31006995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 58 |
E790090
|
entity |
| Predicate | appliedToRoad |
P62312
|
FINISHED |
| Object | Riverina Highway |
—
|
NE NERFINISHED |
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: Riverina Highway | Statement: [State Route 58, appliedToRoad, Riverina Highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToRoad Context triple: [State Route 58, appliedToRoad, Riverina Highway]
-
A.
appliesToRoad
chosen
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a road.
-
B.
appliesToRoadType
Indicates that a rule, condition, or attribute is specifically relevant or valid for a particular type or category of road.
-
C.
onRoad
Indicates that one entity is located on, traveling along, or otherwise situated upon a road.
-
D.
isVisibleFromRoad
Indicates that something can be seen or visually perceived from a road or roadway.
-
E.
appliedToLocationOnVehicle
Indicates that something (such as a treatment, device, or action) is applied specifically to a particular location or area on a vehicle.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: April 29, 2026, 8:57 p.m.