Triple
T19364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidential Medal of Freedom with Distinction |
E383
|
entity |
| Predicate | hasRecipientType |
P379
|
FINISHED |
| Object | individual persons |
—
|
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: individual persons | Statement: [Presidential Medal of Freedom with Distinction, hasRecipientType, individual persons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecipientType Context triple: [Presidential Medal of Freedom with Distinction, hasRecipientType, individual persons]
-
A.
hasTypeOfRecipient
chosen
Indicates that an entity is associated with a specific category or kind of recipient it is intended for or directed to.
-
B.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
C.
coRecipientWith
Indicates that two or more entities receive the same item, benefit, or communication together as joint recipients.
-
D.
hasReception
Indicates that an entity hosts, includes, or is associated with a reception event (such as a formal gathering or welcoming function).
-
E.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
- 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_69a240778d288190815c0052ebbbcc91 |
completed | Feb. 28, 2026, 1:10 a.m. |
| NER | Named-entity recognition | batch_69a246cbca108190a92478df126d9bf8 |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a2464f61648190ac690044be194972 |
completed | Feb. 28, 2026, 1:35 a.m. |
Created at: Feb. 28, 2026, 1:14 a.m.