Triple
T4628899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junkers Ju 86 |
E101164
|
entity |
| Predicate | roleOfVariantJu86P |
P56783
|
FINISHED |
| Object | high‑altitude reconnaissance |
—
|
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: high‑altitude reconnaissance | Statement: [Junkers Ju 86, roleOfVariantJu86P, high‑altitude reconnaissance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfVariantJu86P Context triple: [Junkers Ju 86, roleOfVariantJu86P, high‑altitude reconnaissance]
-
A.
laterVariantRole
chosen
Indicates that one role is a subsequent or later variant of another, reflecting a modified or evolved version of the original role.
-
B.
crewVariantName
Indicates the specific name or label assigned to a particular variant or version of a crew configuration.
-
C.
JapaneseAirCommander
Indicates that one entity serves as a Japanese air force commander in relation to another entity or context.
-
D.
basedAircraftRole
Indicates that an aircraft is regularly stationed at a particular location in a specified operational role or function.
-
E.
aircraftModification
Indicates a relationship where an aircraft undergoes a change, upgrade, or alteration to its structure, systems, or configuration.
- 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.