Triple
T3862674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Distinguished Conduct Medal |
E90175
|
entity |
| Predicate | recipientClass |
P35429
|
FINISHED |
| Object | non-commissioned officers |
—
|
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: non-commissioned officers | Statement: [Distinguished Conduct Medal, recipientClass, non-commissioned officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recipientClass Context triple: [Distinguished Conduct Medal, recipientClass, non-commissioned officers]
-
A.
individualRecipient
Indicates that a specific individual is the direct recipient or beneficiary of something (such as an item, message, or action).
-
B.
receiverType
chosen
Indicates the category or classification of the entity that receives something (such as a message, resource, or action) in the relationship.
-
C.
primaryRecipient
Indicates the entity that is the main or principal receiver of something, such as a message, resource, or benefit, in a given context.
-
D.
organizationRecipient
Indicates that an organization is the recipient or beneficiary of something provided, sent, or directed by another entity.
-
E.
coRecipientWith
Indicates that two or more entities receive the same item, benefit, or communication together as joint recipients.
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec2417648190ad010189d304d119 |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.