Triple
T6358377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin public transport network |
E143047
|
entity |
| Predicate | usesTicketType |
P5937
|
FINISHED |
| Object | single ticket |
—
|
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: single ticket | Statement: [Berlin public transport network, usesTicketType, single ticket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTicketType Context triple: [Berlin public transport network, usesTicketType, single ticket]
-
A.
ticketTypeExample
Indicates that an entity serves as an example or illustrative instance of a particular ticket type.
-
B.
liftTicketType
Indicates the type or category of lift ticket associated with or assigned to an entity.
-
C.
usedInE-tickets
Indicates that something (such as a method, technology, or feature) is employed or applied within the context of electronic tickets (e-tickets).
-
D.
hasTicketRequirement
chosen
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
-
E.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067f5bdd481909cf9db595ddb27df |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ec091c8190912aac44e1b8b1c9 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.