Triple
T19410471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dungog railway station |
E485572
|
entity |
| Predicate | hasLongDistanceServices |
P42175
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Dungog railway station, hasLongDistanceServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLongDistanceServices Context triple: [Dungog railway station, hasLongDistanceServices, yes]
-
A.
longDistanceService
chosen
Indicates that a service operates over large geographic distances, typically connecting locations that are far apart rather than nearby.
-
B.
platformsForLongDistanceServices
Indicates that something serves as a designated platform or set of platforms used for operating or providing long-distance services.
-
C.
hasLongDistancePathAccess
Indicates that an entity has the ability or right to use a path or route that spans a long distance.
-
D.
longDistanceOperator
Indicates that an entity performs telephone or communication services that connect calls over long distances between different geographic areas.
-
E.
hasCommercialServices
Indicates that one entity provides or offers commercial services to another entity or within a specified context.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af4cc0c81909056b5e2ee574ab1 |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.