Triple
T21602998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Param Vir Chakra |
E533095
|
entity |
| Predicate | warTimeOnly |
P144747
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Param Vir Chakra, warTimeOnly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warTimeOnly Context triple: [Param Vir Chakra, warTimeOnly, true]
-
A.
wartimeUse
Indicates that something is used or employed during a period of war or armed conflict.
-
B.
warTimeEvent
Indicates an event that occurs during a period of war or armed conflict, typically as part of or directly influenced by that conflict.
-
C.
wartimeControl
Indicates that one entity exercises authoritative command or governance over another entity specifically during a period of armed conflict or war.
-
D.
warPeriod
Indicates a time span during which a state of war or armed conflict is ongoing between parties.
-
E.
warStatus
Indicates the state or condition of conflict or war that exists between entities at a given time.
- 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_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. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:33 p.m.