Triple
T23114780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First South Yorkshire |
E576718
|
entity |
| Predicate | offersConcession |
P63281
|
FINISHED |
| Object | student 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: student tickets | Statement: [First South Yorkshire, offersConcession, student tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersConcession Context triple: [First South Yorkshire, offersConcession, student tickets]
-
A.
offersPass
Indicates that one entity provides or makes available a pass (such as a ticket, permit, or access credential) to another entity.
-
B.
concessionIncludes
Indicates that one concession contains, comprises, or encompasses another concession as a part or subset.
-
C.
offersObject
chosen
Indicates that a subject provides or makes available a specific object to another party as an offer.
-
D.
concessionFor
Indicates a relationship where one party grants or yields something—such as rights, privileges, or resources—to another, often as part of a negotiation or agreement.
-
E.
offersIncentive
Indicates that one entity provides a reward, benefit, or motivation to another entity to encourage a specific action or behavior.
- 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e11e9dc819093c569f388ffd46b |
completed | April 29, 2026, 4:50 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:59 p.m.