Triple
T36032560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Prospect |
E1042304
|
entity |
| Predicate | hasRailAccessNearby |
P57688
|
FINISHED |
| Object | Gawler railway line |
—
|
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: Gawler railway line | Statement: [City of Prospect, hasRailAccessNearby, Gawler railway line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailAccessNearby Context triple: [City of Prospect, hasRailAccessNearby, Gawler railway line]
-
A.
hasNearbyRailway
Indicates that one entity is located close to a railway associated with or relevant to another entity.
-
B.
hasRailOrRoadAccess
Indicates that an entity is connected to or reachable by either a railway network, a road network, or both.
-
C.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
D.
railwayAccess
chosen
Indicates that an entity has direct access to, connection with, or service by a railway line or station.
-
E.
railAccessModel
Indicates the type or pattern of how rail infrastructure or services are accessed or connected between locations or entities.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: May 3, 2026, 4:07 p.m.