Triple
T4079715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korean War CIB |
E87447
|
entity |
| Predicate | eligibleRecipient |
P14855
|
FINISHED |
| Object | U.S. Army infantry soldiers |
—
|
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: U.S. Army infantry soldiers | Statement: [Korean War CIB, eligibleRecipient, U.S. Army infantry soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleRecipient Context triple: [Korean War CIB, eligibleRecipient, U.S. Army infantry soldiers]
-
A.
recipientOf
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from another entity.
-
B.
individualRecipient
chosen
Indicates that a specific individual is the direct recipient or beneficiary of something (such as an item, message, or action).
-
C.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
-
D.
notableRecipient
Indicates that an entity has received a notable award, honor, or recognition from another entity.
-
E.
organizationRecipient
Indicates that an organization is the recipient or beneficiary of something provided, sent, or directed by another entity.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc5087b081909d6042bfe8d8a306 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.