Triple
T2924491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hobart Airport |
E78809
|
entity |
| Predicate | hasPublicTransportLinks |
P3791
|
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: [Hobart Airport, hasPublicTransportLinks, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicTransportLinks Context triple: [Hobart Airport, hasPublicTransportLinks, true]
-
A.
hasPublicTransportConnection
chosen
Indicates that there is an available public transportation link or service connecting the related entities.
-
B.
hasPublicTransitProvider
Indicates that a place or region is served by a specific public transit operating organization or agency.
-
C.
hasPublicTransitMode
Indicates that a location, route, or service is associated with or supports a specific mode of public transportation (e.g., bus, train, tram).
-
D.
hasPublicTransitRoute
Indicates that there exists a public transportation route (such as a bus, train, or tram line) connecting or serving the related entities.
-
E.
hasPublicTransitRole
Indicates that an entity holds a specific functional role or responsibility within a public transit system.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:55 p.m.