Triple
T32198867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAD |
E822473
|
entity |
| Predicate | associatedServiceBranch |
P116110
|
FINISHED |
| Object | United States Air Force |
E891
|
NE 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: United States Air Force | Statement: [BAD, associatedServiceBranch, United States Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedServiceBranch Context triple: [BAD, associatedServiceBranch, United States Air Force]
-
A.
associatedOrganizationBranch
chosen
Indicates that an entity is connected to or linked with a specific branch or subdivision of an organization.
-
B.
branchServices
Indicates that a particular service is provided or available at a specific branch location.
-
C.
linkedByServiceTo
Indicates that one entity is connected or associated with another through a specific service acting as the linking mechanism.
-
D.
originalServiceBranch
Indicates the military or organizational service branch in which an individual initially served or was first enlisted.
-
E.
relatedService
Indicates that one service is connected or associated with another service in a relevant or dependent way.
- F. None of above.
Provenance (4 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0bc2956c819085fdc70511242b46 |
completed | June 14, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:36 a.m.