Triple
T780030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medal of Honor |
E16474
|
entity |
| Predicate | entitlesRecipientTo |
P168
|
FINISHED |
| Object | Medal of Honor Roll enrollment |
—
|
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: Medal of Honor Roll enrollment | Statement: [Medal of Honor, entitlesRecipientTo, Medal of Honor Roll enrollment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entitlesRecipientTo Context triple: [Medal of Honor, entitlesRecipientTo, Medal of Honor Roll enrollment]
-
A.
notableRecipient
Indicates that an entity has received a notable award, honor, or recognition from another entity.
-
B.
grantedTo
chosen
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
-
C.
recipientsMayUse
Indicates that recipients are permitted to use something (e.g., content, data, or resources) under specified conditions.
-
D.
notableRecipientType
Indicates that an entity is notably recognized as a recipient of something (such as an award, honor, or distinction) of a specified type.
-
E.
leaseRecipient
Indicates the party that receives or holds rights to use a property or asset under a lease agreement from another party.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a90365648190ace53b0f0e87aa68 |
completed | March 1, 2026, 9 p.m. |
| PD | Predicate disambiguation | batch_69a4a50bd23081908908235b8ec9201e |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.