Triple
T29033390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamgha-e-Imtiaz |
E737787
|
entity |
| Predicate | awardedForServicesTo |
P32639
|
FINISHED |
| Object | state of Pakistan |
—
|
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: state of Pakistan | Statement: [Tamgha-e-Imtiaz, awardedForServicesTo, state of Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardedForServicesTo Context triple: [Tamgha-e-Imtiaz, awardedForServicesTo, state of Pakistan]
-
A.
awardedForToReceive
Indicates that an entity is granted an award or recognition in order to receive it for a specific reason, achievement, or qualifying basis.
-
B.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
-
C.
awardedForActivitiesIn
chosen
Indicates that an award or recognition is given to an entity specifically because of activities carried out in a particular field, context, or domain.
-
D.
awardedFrom
Indicates that one entity has received an award, prize, or honor that originates from or is granted by another entity.
-
E.
providesServiceTowards
Indicates that one entity delivers or performs a service directed to or for the benefit of another entity.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 28, 2026, 9:57 a.m.