Triple
T26832902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalyana-Karnataka region |
E675545
|
entity |
| Predicate | hasReservationBenefit |
P2188
|
FINISHED |
| Object | special reservation in education |
—
|
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: special reservation in education | Statement: [Kalyana-Karnataka region, hasReservationBenefit, special reservation in education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReservationBenefit Context triple: [Kalyana-Karnataka region, hasReservationBenefit, special reservation in education]
-
A.
hasBenefit
chosen
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
B.
hasReservationIn
Indicates that an entity holds or possesses a reservation at or within a specified place, service, or event.
-
C.
hasReservationOf
Indicates that one entity holds or possesses a reservation for another entity (such as a service, resource, or event).
-
D.
hasReservationPolicy
Indicates that an entity specifies or is governed by a particular policy regarding how reservations are made, managed, or honored.
-
E.
containsReservation
Indicates that one entity includes or holds a reservation associated with another entity.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: April 27, 2026, 5:02 a.m.