Triple
T22233735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 190th Brigade |
E549532
|
entity |
| Predicate | serviceBranchLater |
P2099
|
FINISHED |
| Object | British Army 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: British Army infantry | Statement: [190th Brigade, serviceBranchLater, British Army infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceBranchLater Context triple: [190th Brigade, serviceBranchLater, British Army infantry]
-
A.
serviceBranch
chosen
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
B.
serviceBranchSpecific
Indicates that something is restricted or tailored to a particular branch of service rather than being common across all branches.
-
C.
serviceBranchLevel
Indicates the hierarchical level or tier within a service branch at which an entity operates or is classified.
-
D.
serviceBranchSupport
Indicates that one entity provides support or assistance to a specific branch of service (such as a military or organizational division).
-
E.
serviceBranchOptions
Indicates the available branches or divisions of service that can be selected or associated with an 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12bf61504819093e70bee4c575d1c |
completed | April 28, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:38 p.m.