Triple
T5738716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieutenant Governors of Union Territories |
E126560
|
entity |
| Predicate | eligibleForAppointment |
P36074
|
FINISHED |
| Object | citizens of India |
—
|
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: citizens of India | Statement: [Lieutenant Governors of Union Territories, eligibleForAppointment, citizens of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleForAppointment Context triple: [Lieutenant Governors of Union Territories, eligibleForAppointment, citizens of India]
-
A.
canHoldAppointment
chosen
Indicates that an entity is eligible or permitted to occupy or serve in a particular appointment, position, or role.
-
B.
canConfirmAppointments
Indicates that an entity has the ability or permission to confirm scheduled appointments.
-
C.
positionEligible
Indicates that an entity is qualified or permitted to hold or be assigned to a particular position or role.
-
D.
eligibleOn
Indicates the date or condition from which something qualifies to begin or be considered valid or applicable.
-
E.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0255dc35c8190ab9ee5d269ce553a |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.