Triple
T17374624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibraltar B-24 crash of 4 July 1943 |
E422403
|
entity |
| Predicate | summary |
P31882
|
FINISHED |
| Object | B-24 Liberator crashed into the sea shortly after takeoff from Gibraltar |
—
|
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: B-24 Liberator crashed into the sea shortly after takeoff from Gibraltar | Statement: [Gibraltar B-24 crash of 4 July 1943, summary, B-24 Liberator crashed into the sea shortly after takeoff from Gibraltar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summary Context triple: [Gibraltar B-24 crash of 4 July 1943, summary, B-24 Liberator crashed into the sea shortly after takeoff from Gibraltar]
-
A.
summarizes
chosen
Indicates that one entity provides a concise representation or overview of the main points or content of another entity.
-
B.
reasoningSummary
Indicates that an entity provides a condensed explanation or overview of the reasoning or logical steps behind a conclusion, decision, or result.
-
C.
outcomeSummary
Indicates a concise description or overview of the result or consequences of an action, event, or process.
-
D.
subtitle
Indicates that one work serves as a secondary or explanatory title to another, typically appearing beneath the main title.
-
E.
typicalConclusion
Indicates that one entity is the usual or expected outcome, result, or ending that follows from another entity or situation.
- 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.