Triple
T25684965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 Census of India |
E644040
|
entity |
| Predicate | referenceLanguageDataYear |
P68415
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [2011 Census of India, referenceLanguageDataYear, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referenceLanguageDataYear Context triple: [2011 Census of India, referenceLanguageDataYear, 2011]
-
A.
translationYear
Indicates the year in which something (typically a work or text) was translated into another language.
-
B.
yearOfReference
chosen
Indicates the specific year to which a statement, measurement, or data point is intended to apply or be interpreted with reference.
-
C.
yearObserved
Indicates the specific calendar year during which the referenced event, condition, or measurement was observed or recorded.
-
D.
declaredYear
Indicates the year in which something was formally announced, established, or proclaimed.
-
E.
nationalYears
Indicates the span of years during which an entity was active or affiliated at the national level (e.g., on a national team or in a national role).
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 8:06 p.m.