Triple
T1894476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Airborne Corps |
E41946
|
entity |
| Predicate | militaryBranchSpecialization |
P8360
|
FINISHED |
| Object | airborne forces |
—
|
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: airborne forces | Statement: [I Airborne Corps, militaryBranchSpecialization, airborne forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryBranchSpecialization Context triple: [I Airborne Corps, militaryBranchSpecialization, airborne forces]
-
A.
militaryBranchEmphasis
chosen
Indicates a relationship where a military branch is given particular focus, priority, or specialization within a broader military or organizational context.
-
B.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
C.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
-
D.
hasMilitaryBranch
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
E.
militarySystem
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb1497df08190ad90dd89f76208ca |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe7e7e88190b58c0df59187c0c2 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.