Triple
T8560163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overseas Citizen of India |
E202670
|
entity |
| Predicate | mergedEffectiveDate |
P21874
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Overseas Citizen of India, mergedEffectiveDate, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedEffectiveDate Context triple: [Overseas Citizen of India, mergedEffectiveDate, 2015]
-
A.
consolidationDate
chosen
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
B.
decisionEffectiveDate
Indicates the date on which a particular decision becomes valid, operative, or officially takes effect.
-
C.
extensionEffectiveDate
Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
-
D.
effectiveForPaymentsMadeAfter
Indicates that a condition, rule, or agreement applies only to payments that are made after a specified time or event.
-
E.
currentVersionEffectiveDate
Indicates the date from which the current version of an item, record, or agreement becomes valid and in effect.
- 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.