Triple
T111933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Naval Air Service |
E2266
|
entity |
| Predicate | militaryBranchType |
P253
|
FINISHED |
| Object | air force |
—
|
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: air force | Statement: [Royal Naval Air Service, militaryBranchType, air force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryBranchType Context triple: [Royal Naval Air Service, militaryBranchType, air force]
-
A.
hasMilitaryBranch
chosen
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
B.
hasMilitaryDivision
Indicates that an entity possesses, includes, or is organizationally associated with a specific military division.
-
C.
primaryUSForces
Indicates that the referenced forces constitute the main or principal contingent of United States military forces in a given context or operation.
-
D.
hasCadetBranch
Indicates that one lineage, family, or house is a junior or offshoot branch derived from another main or senior line.
-
E.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256425a488190959d71e39e699d90 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.