Triple
T21602981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Param Vir Chakra |
E533095
|
entity |
| Predicate | retroactiveFrom |
P36523
|
FINISHED |
| Object | 1947-08-15 |
—
|
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: 1947-08-15 | Statement: [Param Vir Chakra, retroactiveFrom, 1947-08-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retroactiveFrom Context triple: [Param Vir Chakra, retroactiveFrom, 1947-08-15]
-
A.
isRetroactive
chosen
Indicates that an action, rule, or effect applies to a time period before its creation, enactment, or implementation.
-
B.
doesNotApplyRetroactivelyTo
Indicates that a rule, law, or condition does not affect events, actions, or situations that occurred before it came into effect.
-
C.
retrocessionDate
Indicates the date on which rights, obligations, or control previously transferred are formally returned or reassigned back to the original party or another designated party.
-
D.
retrocededTo
Indicates that control, ownership, or rights over something were returned or transferred back from one entity to another.
-
E.
transitionDate
Indicates the date on which a change from one state, status, or condition to another takes place.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e31c80819090fdd63b5c103acb |
completed | April 27, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.