Triple
T5596530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hell Week |
E147010
|
entity |
| Predicate | selectionFunction |
P126
|
FINISHED |
| Object | eliminate majority of BUD/S attrition |
—
|
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: eliminate majority of BUD/S attrition | Statement: [Hell Week, selectionFunction, eliminate majority of BUD/S attrition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionFunction Context triple: [Hell Week, selectionFunction, eliminate majority of BUD/S attrition]
-
A.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
B.
selectionCharacteristic
Indicates a distinguishing feature or criterion used to choose or differentiate one entity from others.
-
C.
selectionFrom
Indicates that one entity is chosen as a member or subset from a larger set or collection represented by another entity.
-
D.
selectionProcess
chosen
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
-
E.
selectionMadeBy
Indicates that a particular choice or selection was performed or decided by a specific agent or 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020bf77cc8190b8ca473c3a2e1d28 |
completed | March 22, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.