Triple
T3417139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hallesches Tor |
E72035
|
entity |
| Predicate | hasTicketZoneCode |
P42683
|
FINISHED |
| Object | A |
—
|
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: A | Statement: [Hallesches Tor, hasTicketZoneCode, A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketZoneCode Context triple: [Hallesches Tor, hasTicketZoneCode, A]
-
A.
ticketingZoneType
Indicates the type or category of ticketing zone that applies within a given area or context.
-
B.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
C.
ticketingCode
chosen
Indicates the specific fare or booking code associated with a ticket that defines its pricing, rules, and conditions of use.
-
D.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
E.
hasTicketRequirement
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb92c20fc81909b5debced20ec083 |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.