Triple
T33289367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheffield PlusBus area |
E852271
|
entity |
| Predicate | ticketValidityCondition |
P159395
|
FINISHED |
| Object | must be bought with rail 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: must be bought with rail ticket | Statement: [Sheffield PlusBus area, ticketValidityCondition, must be bought with rail ticket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketValidityCondition Context triple: [Sheffield PlusBus area, ticketValidityCondition, must be bought with rail ticket]
-
A.
ticketValidityCovers
Indicates that the validity period or scope of a ticket extends to and includes a specified time, location, service, or condition.
-
B.
ticketInspectionRule
chosen
Indicates the rule or condition under which tickets are to be inspected or validated.
-
C.
ticketTypeAccepted
Indicates that a particular type of ticket is valid for use or accepted in a given context or by a given entity.
-
D.
hasTicket
Indicates that an entity possesses or holds a ticket, typically granting access, entry, or a right to a service or event.
-
E.
ticketTypeStored
Indicates that a particular type of ticket has been recorded and saved in a storage or system.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:32 a.m.