Triple
T22120254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dindori (Lok Sabha constituency) |
E546645
|
entity |
| Predicate | hasReservationCategory |
P45275
|
FINISHED |
| Object | ST |
—
|
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: ST | Statement: [Dindori (Lok Sabha constituency), hasReservationCategory, ST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReservationCategory Context triple: [Dindori (Lok Sabha constituency), hasReservationCategory, ST]
-
A.
hasReservationType
chosen
Indicates that an entity is associated with a specific category or type of reservation.
-
B.
hasReservationIn
Indicates that an entity holds or possesses a reservation at or within a specified place, service, or event.
-
C.
hasTicketCategory
Indicates that an item, event, or access right is associated with a specific ticket category or type.
-
D.
hasReservationStatus
Indicates that an entity is associated with a specific reservation and the current status or state of that reservation (e.g., pending, confirmed, canceled).
-
E.
hasCheckInCategory
Indicates that an entity is associated with a specific category or type of check-in event.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12951fcd48190841319cd879c15cb |
completed | April 28, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.