Triple
T17374652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibraltar B-24 crash of 4 July 1943 |
E422403
|
entity |
| Predicate | crewInvolved |
P24309
|
FINISHED |
| Object | Royal Air Force crew |
—
|
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: Royal Air Force crew | Statement: [Gibraltar B-24 crash of 4 July 1943, crewInvolved, Royal Air Force crew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewInvolved Context triple: [Gibraltar B-24 crash of 4 July 1943, crewInvolved, Royal Air Force crew]
-
A.
crewInvolvedIn
chosen
Indicates that a crew (as a group or unit) participates in, contributes to, or is otherwise involved in a specified event, activity, or operation.
-
B.
crewCount
Indicates the number of crew members associated with an entity, such as a vehicle, vessel, or mission.
-
C.
crewOnboard
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
D.
crew
Indicates that one entity serves as the group of people who operate, staff, or work on another entity (such as a vehicle, vessel, or production).
-
E.
crewRequired
Indicates that a certain number or type of crew members is necessary to operate or support the associated entity or activity.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6b71148190bb10e1fac400d6c3 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.