Triple
T36992869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shuhada of Pakistan Armed Forces |
E915151
|
entity |
| Predicate | haveMemorials |
P501
|
FINISHED |
| Object | monuments and memorials across 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: monuments and memorials across Pakistan | Statement: [Shuhada of Pakistan Armed Forces, haveMemorials, monuments and memorials across Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveMemorials Context triple: [Shuhada of Pakistan Armed Forces, haveMemorials, monuments and memorials across Pakistan]
-
A.
hasGraveOrMemorialOf
Indicates that a location or object serves as the grave or memorial site dedicated to a particular person or entity.
-
B.
hasMemorial
chosen
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
C.
hasNearbyMemorials
Indicates that one or more memorials are located in close physical proximity to the referenced entity.
-
D.
relatedMemorial
Indicates a relationship where one entity serves as a memorial or commemorative reference to another entity.
-
E.
memorialWork
Indicates that one entity is a commemorative work (such as a monument, plaque, or artwork) created to honor or remember 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.