Triple
T16193078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shiny Six |
E392990
|
entity |
| Predicate | appliesToUnitBranch |
P70948
|
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: [Shiny Six, appliesToUnitBranch, air force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToUnitBranch Context triple: [Shiny Six, appliesToUnitBranch, air force]
-
A.
relatesToBranch
Indicates a general association or connection between an entity and a specific branch (such as a subdivision, offshoot, or subunit) within a larger structure or system.
-
B.
usedByBranch
Indicates that something (such as a resource, configuration, or component) is utilized or depended upon by a particular branch.
-
C.
refersToServiceBranch
chosen
Indicates that one entity is associated with, or designates, a particular branch of a service organization (such as a military or similar structured service).
-
D.
presentInBranch
Indicates that something exists or is available within a specific branch or subdivision of a larger organization or structure.
-
E.
supportingBranch
Indicates that one branch structurally or functionally supports another branch.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222d74d788190a637fdb9b4f184b9 |
completed | April 17, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.