Triple
T13088963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pooncarie |
E310408
|
entity |
| Predicate | roadNetworkContext |
P107985
|
FINISHED |
| Object | rural roads of far south-west NSW |
—
|
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: rural roads of far south-west NSW | Statement: [Pooncarie, roadNetworkContext, rural roads of far south-west NSW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadNetworkContext Context triple: [Pooncarie, roadNetworkContext, rural roads of far south-west NSW]
-
A.
streetNetwork
Indicates the layout and connectivity relationships among streets within a geographic area, including how roads intersect, link, and form a navigable network.
-
B.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
C.
roadNetworkPartOf
Indicates that one road network segment or component is a constituent part of a larger road network.
-
D.
roadNetworkJurisdiction
Indicates the authority or entity responsible for managing, regulating, or maintaining a given segment of the road network.
-
E.
roadNetworkConformsTo
Indicates that a road network adheres to, or is compliant with, a specified standard, specification, or reference model.
- F. None of above. chosen
Provenance (4 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d98138a1d481908a139f2f67eb3472 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98114a6508190b1e8e018bb5a068c |
completed | April 10, 2026, 11 p.m. |
Created at: April 9, 2026, 9:02 p.m.