Triple
T1277040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Param Vishisht Seva Medal |
E27237
|
entity |
| Predicate | peacetimeOrWartime |
P26008
|
FINISHED |
| Object | peacetime |
—
|
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: peacetime | Statement: [Param Vishisht Seva Medal, peacetimeOrWartime, peacetime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peacetimeOrWartime Context triple: [Param Vishisht Seva Medal, peacetimeOrWartime, peacetime]
-
A.
warPeriod
Indicates a time span during which a state of war or armed conflict is ongoing between parties.
-
B.
peacetimeOperation
chosen
Indicates that an entity is engaged in activities or functions carried out under normal, non-wartime conditions.
-
C.
statusDuringWar
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
D.
enemyDuringWar
Indicates that one entity is an enemy of another specifically in the context of a particular war or armed conflict.
-
E.
wartimeControl
Indicates that one entity exercises authoritative command or governance over another entity specifically during a period of armed conflict or war.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.