Triple
T13678218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunter Valley rail network |
E327929
|
entity |
| Predicate | hasTrafficDensity |
P29452
|
FINISHED |
| Object | high freight train frequency |
—
|
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: high freight train frequency | Statement: [Hunter Valley rail network, hasTrafficDensity, high freight train frequency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrafficDensity Context triple: [Hunter Valley rail network, hasTrafficDensity, high freight train frequency]
-
A.
hasHeavyTraffic
Indicates that a location, route, or area is experiencing a high volume of traffic, causing congestion or delays.
-
B.
hasTrafficPattern
chosen
Indicates that there is a characteristic or recurring flow of traffic associated with an entity, such as its typical volume, direction, or timing of movement.
-
C.
hasTrafficFeature
Indicates that an entity possesses or is associated with a specific traffic-related characteristic, element, or infrastructure feature.
-
D.
hasTrafficRegime
Indicates that a specified traffic control or regulatory system applies to a given road, area, or transport context.
-
E.
hasTruckTraffic
Indicates that there is truck-related vehicular movement or flow occurring on or through a specified location or route.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc65d8dc081909664e69bb38610ba |
completed | April 12, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.