Triple
T29421677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helsinki City Ferry to Suomenlinna |
E746171
|
entity |
| Predicate | usesTicketZone |
P177562
|
FINISHED |
| Object | Helsinki internal zone |
—
|
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: Helsinki internal zone | Statement: [Helsinki City Ferry to Suomenlinna, usesTicketZone, Helsinki internal zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTicketZone Context triple: [Helsinki City Ferry to Suomenlinna, usesTicketZone, Helsinki internal zone]
-
A.
ticketZoneSystem
Indicates that there is a specific fare or access zoning system governing how tickets are defined, priced, or validated within a transport or event context.
-
B.
hasTicketZoneOperator
Indicates that a ticket zone is managed, controlled, or operated by a specific operator.
-
C.
ticketingZoneType
Indicates the type or category of ticketing zone that applies within a given area or context.
-
D.
usedForTicketType
Indicates that something is utilized or applicable for a specific type or category of ticket.
-
E.
fareZoneIncludes
Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
- F. None of above. chosen
Provenance (4 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 28, 2026, 3:06 p.m.