Triple
T3373368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthony Skingsley |
E71005
|
entity |
| Predicate | armedForceRole |
P9463
|
FINISHED |
| Object | air defence leadership |
—
|
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 defence leadership | Statement: [Anthony Skingsley, armedForceRole, air defence leadership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedForceRole Context triple: [Anthony Skingsley, armedForceRole, air defence leadership]
-
A.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
militaryFunction
Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military context.
-
C.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
D.
peacetimeRole
Indicates the role, function, or duties an entity holds during periods of peace rather than during wartime or conflict.
-
E.
militaryResponsibility
Indicates that an entity holds authority, duty, or accountability for military actions, operations, or forces in relation 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2bdcf70819087fc7e00fbd61e0d |
completed | March 8, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.