Triple
T26199432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Register of Citizens in Assam |
E655191
|
entity |
| Predicate | cutoffDateForInclusion |
P160736
|
FINISHED |
| Object | 24 March 1971 |
—
|
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: 24 March 1971 | Statement: [National Register of Citizens in Assam, cutoffDateForInclusion, 24 March 1971]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cutoffDateForInclusion Context triple: [National Register of Citizens in Assam, cutoffDateForInclusion, 24 March 1971]
-
A.
cutOffDateYear
Indicates the calendar year that serves as the cutoff point beyond which something no longer applies, is valid, or is considered.
-
B.
fullContainmentDate
Indicates that one time period or date range is entirely contained within another, without extending beyond its start or end dates.
-
C.
startDateRule
Indicates the rule or condition that determines when something is allowed or required to start.
-
D.
effectiveForPaymentsMadeAfter
Indicates that a condition, rule, or agreement applies only to payments that are made after a specified time or event.
-
E.
startDateConstraint
Indicates a restriction or condition placed on when something is allowed to start, typically specifying valid or required start dates.
- F. None of above. chosen
Provenance (4 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cd9e50481908d1559e6ec048bc1 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f603b90c94819088d62cb9489e95ff |
completed | May 2, 2026, 2:01 p.m. |
Created at: April 26, 2026, 8:47 p.m.