Triple
T1416162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boulton Paul Defiant |
E31921
|
entity |
| Predicate | combatDebut |
P27531
|
FINISHED |
| Object | 1940 |
—
|
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: 1940 | Statement: [Boulton Paul Defiant, combatDebut, 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatDebut Context triple: [Boulton Paul Defiant, combatDebut, 1940]
-
A.
battleOpponent
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
B.
introducedToCombat
Indicates that something was brought into use or implemented specifically for the purpose of addressing or mitigating a particular problem, threat, or undesirable condition.
-
C.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
D.
mainBattle
Indicates that one battle is the primary or most significant engagement associated with a particular conflict, campaign, or entity.
-
E.
openingMatch
Indicates that one entity serves as the initial or first match, game, or contest in a series, event, or competition involving another entity.
- F. None of above. chosen
Provenance (4 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c402b1648190b87802d9beb2712e |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c06721488190ac7f6e012f21af3d |
completed | March 1, 2026, 10:40 p.m. |
Created at: March 1, 2026, 7:59 p.m.