Triple
T8560177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overseas Citizen of India |
E202670
|
entity |
| Predicate | ineligiblePersons |
P50612
|
FINISHED |
| Object | citizens of Pakistan |
—
|
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 Pakistan | Statement: [Overseas Citizen of India, ineligiblePersons, citizens of Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ineligiblePersons Context triple: [Overseas Citizen of India, ineligiblePersons, citizens of Pakistan]
-
A.
nonEligibility
chosen
Indicates that an entity does not meet the required conditions or criteria to qualify for a specified status, benefit, or action.
-
B.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
-
C.
eligibleOn
Indicates the date or condition from which something qualifies to begin or be considered valid or applicable.
-
D.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
E.
eligibilityCategory
Indicates the classification or type of eligibility that applies to an entity within 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe949974c8190a75d9c767ca5fa5a |
completed | March 31, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:20 p.m.