Triple
T35604374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devonport, Tasmania |
E1028843
|
entity |
| Predicate | hasRailFreightTerminal |
P2420
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Devonport, Tasmania, hasRailFreightTerminal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailFreightTerminal Context triple: [Devonport, Tasmania, hasRailFreightTerminal, true]
-
A.
hasRailFacility
Indicates that an entity possesses or is served by a rail-related facility, such as a railway station, terminal, or yard.
-
B.
isRegionalFreightRailroad
Indicates that a railroad operates primarily as a freight carrier within a specific geographic region rather than on a national or long-distance network.
-
C.
railwayTerminalServed
Indicates that a railway terminal is served by, or has service connections with, a particular railway line, route, or operator.
-
D.
hasCargoTerminal
chosen
Indicates that a location or facility includes or is equipped with a cargo terminal for handling freight.
-
E.
hasRailOrRoadAccess
Indicates that an entity is connected to or reachable by either a railway network, a road network, or both.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4:05 p.m.