Triple
T29265061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakistan Honours System |
E741956
|
entity |
| Predicate | includesGallantryAward |
P200644
|
FINISHED |
| Object | Nishan-e-Haider |
—
|
NE NERFINISHED |
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: Nishan-e-Haider | Statement: [Pakistan Honours System, includesGallantryAward, Nishan-e-Haider]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesGallantryAward Context triple: [Pakistan Honours System, includesGallantryAward, Nishan-e-Haider]
-
A.
isGallantryAward
Indicates that the subject is a formal gallantry award, i.e., an honor conferred in recognition of exceptional bravery or valor.
-
B.
rankInGallantryAwards
Indicates the position or level an entity holds within a hierarchy or ordering of gallantry awards.
-
C.
describesGallantryOf
Indicates a relationship where one entity characterizes, explains, or details the gallant or brave behavior of another entity.
-
D.
isMilitaryAwardFor
Indicates that something is a military honor or decoration given in recognition of a specific action, service, or achievement.
-
E.
militaryAward
Indicates that an entity has received or been granted a specific military honor, decoration, or award.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69ff9d9ba1ac8190a0cca5764bb5904d |
completed | May 9, 2026, 8:48 p.m. |
Created at: April 28, 2026, 12:44 p.m.