Triple
T1416166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boulton Paul Defiant |
E31921
|
entity |
| Predicate | laterPrimaryRole |
P27532
|
FINISHED |
| Object | night fighter |
—
|
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: night fighter | Statement: [Boulton Paul Defiant, laterPrimaryRole, night fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPrimaryRole Context triple: [Boulton Paul Defiant, laterPrimaryRole, night fighter]
-
A.
secondaryPosition
Indicates that an entity holds an additional, non-primary role, location, or status alongside its main one.
-
B.
primaryPosition
Indicates the main role, job, or position an entity holds among potentially multiple positions.
-
C.
successorStateRole
Indicates that one role represents the state or position that directly follows and replaces another role in a sequence or process.
-
D.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
E.
laterMember
Indicates that one entity became a member of a group or organization at a later time than 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.