Triple
T26164152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vickers Type 271 design studies |
E654200
|
entity |
| Predicate | aircraftRoleConcept |
P160976
|
FINISHED |
| Object | day bomber |
—
|
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: day bomber | Statement: [Vickers Type 271 design studies, aircraftRoleConcept, day bomber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftRoleConcept Context triple: [Vickers Type 271 design studies, aircraftRoleConcept, day bomber]
-
A.
aircraftRoleConcept
chosen
Indicates the functional role or purpose an aircraft has within a particular context or operation.
-
B.
aircraftRoleSpecialization
Indicates that one aircraft role is a more specific, specialized form of another, more general aircraft role.
-
C.
notableAircraftRole
Indicates that an aircraft is notably associated with performing a particular role or function.
-
D.
aircraftRoleDesignedFor
Indicates that an aircraft is specifically designed or intended to perform a particular role or function.
-
E.
primaryAircraftRole
Indicates the main operational function or mission type an aircraft is primarily designed or used to perform.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 8:31 p.m.