Triple
T19192040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garib Rath Express |
E469862
|
entity |
| Predicate | ticketQuota |
P134810
|
FINISHED |
| Object | general quota |
—
|
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: general quota | Statement: [Garib Rath Express, ticketQuota, general quota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketQuota Context triple: [Garib Rath Express, ticketQuota, general quota]
-
A.
ticketDemand
Indicates that there is a level of desire or need among potential buyers for tickets to an event, service, or offering.
-
B.
ticketReservation
Indicates the act of securing one or more tickets in advance for a specific event, service, or journey.
-
C.
ticketsSold
Indicates that a certain number of tickets have been purchased or distributed for a particular event or offering.
-
D.
ticketingScope
Indicates the range or domain within which ticketing actions (such as creation, assignment, or management of tickets) are valid or applicable.
-
E.
ticketTypeSold
Indicates that a specific type of ticket has been sold in a given transaction or context.
- F. None of above. chosen
Provenance (4 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f8a3434881908acc4063a9ee9386 |
completed | April 20, 2026, 9:57 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:07 p.m.