Triple
T36178529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U-Bahn |
E1046642
|
entity |
| Predicate | commonTicketMedium |
P42387
|
FINISHED |
| Object | paper tickets |
—
|
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: paper tickets | Statement: [U-Bahn, commonTicketMedium, paper tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonTicketMedium Context triple: [U-Bahn, commonTicketMedium, paper tickets]
-
A.
ticketMediumType
chosen
Indicates the type or format of the medium through which a ticket is issued, stored, or presented (e.g., paper, mobile, electronic).
-
B.
ticketTypeCommon
Indicates that two or more tickets share the same general type or classification.
-
C.
hasTicketMedia
Indicates that an entity possesses or is associated with a particular form or medium of a ticket (e.g., paper, digital, mobile).
-
D.
ticket
Indicates that an entity serves as or is associated with a ticket, typically representing authorization, access, or a record for an event, service, or transaction.
-
E.
typicalTicketText
Indicates that the associated text represents the standard or commonly used wording for a ticket.
- 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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: May 3, 2026, 4:08 p.m.