Triple
T5064397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messerschmitt |
E114107
|
entity |
| Predicate | Bf 109Role |
P2860
|
FINISHED |
| Object | primary single-seat fighter of the Luftwaffe |
—
|
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: primary single-seat fighter of the Luftwaffe | Statement: [Messerschmitt, Bf 109Role, primary single-seat fighter of the Luftwaffe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Bf 109Role Context triple: [Messerschmitt, Bf 109Role, primary single-seat fighter of the Luftwaffe]
-
A.
basedAircraftRole
Indicates that an aircraft is regularly stationed at a particular location in a specified operational role or function.
-
B.
primaryGermanFighterAircraft
Indicates that the subject is the main or principal fighter aircraft used by Germany in a given context or time period.
-
C.
primaryAircraftRole
chosen
Indicates the main operational function or mission type an aircraft is primarily designed or used to perform.
-
D.
notableAircraftRole
Indicates that an aircraft is notably associated with performing a particular role or function.
-
E.
testAircraftRole
Indicates that an aircraft is assigned or evaluated for a specific operational role or function.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd747756bc8190863c426e6fd6e8f7 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.