Triple
T16515690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Hero of Afghanistan |
E401176
|
entity |
| Predicate | uniqueRecipient |
P123849
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [National Hero of Afghanistan, uniqueRecipient, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniqueRecipient Context triple: [National Hero of Afghanistan, uniqueRecipient, true]
-
A.
individualRecipient
Indicates that a specific individual is the direct recipient or beneficiary of something (such as an item, message, or action).
-
B.
foreignRecipient
Indicates that something is received by an entity located in or belonging to a different country or jurisdiction than the source.
-
C.
coRecipientWith
Indicates that two or more entities receive the same item, benefit, or communication together as joint recipients.
-
D.
recipientSport
Indicates that one entity is the sport associated with, received by, or designated for another entity.
-
E.
primaryRecipient
Indicates the entity that is the main or principal receiver of something, such as a message, resource, or benefit, in a given context.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7bbfa481909037148cdb4d8996 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:14 a.m.