Triple
T11694759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dworzec Wileński metro station |
E277962
|
entity |
| Predicate | ticketZone |
P74693
|
FINISHED |
| Object | Zone 1 |
—
|
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: Zone 1 | Statement: [Dworzec Wileński metro station, ticketZone, Zone 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketZone Context triple: [Dworzec Wileński metro station, ticketZone, Zone 1]
-
A.
ticketingZoneType
Indicates the type or category of ticketing zone that applies within a given area or context.
-
B.
ticketingLocation
Indicates the place or point where tickets are issued, sold, or otherwise processed for an event, service, or journey.
-
C.
ticketingScope
Indicates the range or domain within which ticketing actions (such as creation, assignment, or management of tickets) are valid or applicable.
-
D.
ticketAcceptanceArea
chosen
Indicates the geographic or operational area within which a given ticket is valid for use or accepted as proof of payment.
-
E.
ticketedAttraction
Indicates that access to the attraction requires a purchased ticket or paid admission.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47b9eb48190976a35e91e25b56b |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.