Triple
T34475616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halyard Mission |
E885023
|
entity |
| Predicate | notableRescuedGroup |
P166896
|
FINISHED |
| Object | United States Army Air Forces airmen |
—
|
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: United States Army Air Forces airmen | Statement: [Halyard Mission, notableRescuedGroup, United States Army Air Forces airmen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRescuedGroup Context triple: [Halyard Mission, notableRescuedGroup, United States Army Air Forces airmen]
-
A.
rescuedBy
Indicates that one entity has been saved or brought out of danger by another entity.
-
B.
rescuedDuring
Indicates that one entity was rescued in the course of, or as part of, a specified event or time period.
-
C.
rescuesGroup
chosen
Indicates that one entity saves or frees a group of entities from danger, harm, or a problematic situation.
-
D.
notableRescuer
Indicates that one entity is recognized for having performed a significant or noteworthy act of rescuing another entity.
-
E.
rescuedTo
Indicates that one entity has been saved or freed from danger, harm, or a problematic situation and brought to the safety or custody of another entity or location.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:01 a.m.