Triple
T10078256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinkel He 277 |
E213828
|
entity |
| Predicate | airForceRoleIntended |
P9463
|
FINISHED |
| Object | Luftwaffe strategic bomber force |
—
|
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: Luftwaffe strategic bomber force | Statement: [Heinkel He 277, airForceRoleIntended, Luftwaffe strategic bomber force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airForceRoleIntended Context triple: [Heinkel He 277, airForceRoleIntended, Luftwaffe strategic bomber force]
-
A.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
usedByAirForce
Indicates that something is employed, operated, or otherwise utilized by an air force.
-
C.
favoredMilitaryRole
Indicates the military position, function, or specialization that an entity prefers or is most inclined to choose.
-
D.
airForceDesignation
Indicates that one entity is the official designation or code assigned to something by an air force.
-
E.
airWingPersonnel
Indicates that the subject is a member of, or assigned as personnel to, an air wing unit.
- 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_69ca839bf730819086900c323c9b8c95 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd030a0fc819084b523e8e63636fa |
completed | April 2, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9 p.m.