Triple
T4628911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junkers Ju 86 |
E101164
|
entity |
| Predicate | enteredLuftwaffeService |
P38201
|
FINISHED |
| Object | late 1930s |
—
|
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: late 1930s | Statement: [Junkers Ju 86, enteredLuftwaffeService, late 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredLuftwaffeService Context triple: [Junkers Ju 86, enteredLuftwaffeService, late 1930s]
-
A.
serviceEntryWithLuftwaffe
chosen
Indicates that an entity’s service entry or enlistment is associated with the Luftwaffe (the German air force).
-
B.
enteredUSAAFService
Indicates that an entity began active service in the United States Army Air Forces.
-
C.
commanderOfLuftwaffe
Indicates that one entity serves as the commanding officer or leader of the Luftwaffe (the German air force).
-
D.
primaryGermanFighterAircraft
Indicates that the subject is the main or principal fighter aircraft used by Germany in a given context or time period.
-
E.
enteredRAFService
Indicates that an entity began service in the Royal Air Force (RAF).
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a300e6081909fa9f504aada33ea |
completed | March 20, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.