Triple
T10172986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donald Malarkey |
E235777
|
entity |
| Predicate | serviceBranchSpecialization |
P2099
|
FINISHED |
| Object | airborne infantry |
—
|
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: airborne infantry | Statement: [Donald Malarkey, serviceBranchSpecialization, airborne infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceBranchSpecialization Context triple: [Donald Malarkey, serviceBranchSpecialization, airborne infantry]
-
A.
serviceBranchSpecific
Indicates that something is restricted or tailored to a particular branch of service rather than being common across all branches.
-
B.
serviceBranch
chosen
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
C.
serviceBranchLevel
Indicates the hierarchical level or tier within a service branch at which an entity operates or is classified.
-
D.
serviceBranchOptions
Indicates the available branches or divisions of service that can be selected or associated with an entity.
-
E.
serviceBranchSupport
Indicates that one entity provides support or assistance to a specific branch of service (such as a military or organizational division).
- 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_69ca84d1d5f88190ab878a1021ecff68 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec9f6dd8819081588600499165ee |
completed | April 2, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:10 p.m.