Triple
T12889319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupolev Tu-10 |
E308315
|
entity |
| Predicate | militaryBranchIntended |
P253
|
FINISHED |
| Object | Soviet military aviation |
—
|
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: Soviet military aviation | Statement: [Tupolev Tu-10, militaryBranchIntended, Soviet military aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryBranchIntended Context triple: [Tupolev Tu-10, militaryBranchIntended, Soviet military aviation]
-
A.
militaryBranchEmphasis
Indicates a relationship where a military branch is given particular focus, priority, or specialization within a broader military or organizational context.
-
B.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
-
C.
hasMilitaryBranch
chosen
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
D.
militaryBranchDomain
Indicates that one entity serves as the military branch or armed forces component associated with the domain, jurisdiction, or organizational scope of another entity.
-
E.
favoredMilitaryRole
Indicates the military position, function, or specialization that an entity prefers or is most inclined to choose.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714581988190afc720ffd7797860 |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:39 p.m.