Triple
T6318423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Officer Commanding No. 11 Group RAF |
E141672
|
entity |
| Predicate | isMilitaryBranchPosition |
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: [Air Officer Commanding No. 11 Group RAF, isMilitaryBranchPosition, air force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMilitaryBranchPosition Context triple: [Air Officer Commanding No. 11 Group RAF, isMilitaryBranchPosition, air force]
-
A.
isMilitaryOfficer
Indicates that the subject holds an official position as an officer within a military organization.
-
B.
isMilitaryRank
Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
-
C.
isMilitaryPostType
Indicates that something is classified as a type or category of military post or installation.
-
D.
hasMilitaryBranch
chosen
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
E.
isFlagOfficerPosition
Indicates that a position is designated for or held by a flag officer within a military hierarchy.
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064c38fe48190a71a4e5e1af19b10 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.