Triple
T198369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bharat Ratna |
E4046
|
entity |
| Predicate | eligibilityExpandedInYear |
P1130
|
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: [Bharat Ratna, eligibilityExpandedInYear, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibilityExpandedInYear Context triple: [Bharat Ratna, eligibilityExpandedInYear, 2011]
-
A.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
B.
eligibilityCriteria
chosen
Indicates the conditions or requirements that must be satisfied for an entity to qualify for or be considered eligible for something.
-
C.
dropEligibleIndicatorSizeBits
Indicates whether an entity is eligible to be dropped, encoded as a bit-sized indicator value.
-
D.
authorizationYear
Indicates the year in which an official approval, permission, or authorization for something was granted.
-
E.
expandedSignificantlyInYear
Indicates that an entity underwent a substantial increase or growth during a specified year.
- 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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25be47ea881909c296b30a0d47a65 |
completed | Feb. 28, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69a25b47481c8190add47c641c977bb9 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.