Triple
T25960991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaheed Rafiq |
E645536
|
entity |
| Predicate | isHonoredAs |
P74359
|
FINISHED |
| Object | martyr |
—
|
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: martyr | Statement: [Shaheed Rafiq, isHonoredAs, martyr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHonoredAs Context triple: [Shaheed Rafiq, isHonoredAs, martyr]
-
A.
alsoHonoredAs
Indicates that an entity is additionally recognized or celebrated under another title, role, or form of honor beyond its primary designation.
-
B.
namedInHonorBy
Indicates that one entity has been used as the namesake or dedicatee by another entity, signifying that the latter is named in honor of the former.
-
C.
isGivenInHonorOf
Indicates that something (such as an award, gift, or event) is presented or dedicated as a mark of respect or recognition for a particular person or entity.
-
D.
honoredPerson
Indicates that a person is the recipient of honor, recognition, or special distinction from another party or in a particular context.
-
E.
celebratedAs
chosen
Indicates that one entity is regarded, honored, or widely recognized as having a particular role, status, or distinction.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f604c60fe0819092ad09d1c5b0c100 |
completed | May 2, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:47 a.m.