Triple
T31395038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-ville |
E800841
|
entity |
| Predicate | ticketPolicyContext |
P145060
|
FINISHED |
| Object | student ticket lottery |
—
|
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 ticket lottery | Statement: [K-ville, ticketPolicyContext, student ticket lottery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketPolicyContext Context triple: [K-ville, ticketPolicyContext, student ticket lottery]
-
A.
ticketingContext
chosen
Indicates the situational or operational context in which a ticket (such as a support, event, or issue ticket) is created, managed, or applied.
-
B.
ticketPricePolicy
Indicates the pricing rules or conditions that determine how much a ticket costs in a given context.
-
C.
ticketInspectionRule
Indicates the rule or condition under which tickets are to be inspected or validated.
-
D.
farePolicyAspect
Indicates a specific rule, condition, or feature that characterizes some aspect of a fare policy.
-
E.
passengerPolicy
Indicates the rules or conditions governing whether and how passengers are allowed or managed in a given context.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:19 p.m.