Triple
T3771901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armed Forces of Belarus |
E83216
|
entity |
| Predicate | serviceBranchesInclude |
P2099
|
FINISHED |
| Object | army |
—
|
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: army | Statement: [Armed Forces of Belarus, serviceBranchesInclude, army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceBranchesInclude Context triple: [Armed Forces of Belarus, serviceBranchesInclude, army]
-
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.
servesBranch
Indicates that one entity provides services or support to a particular branch or subdivision of an organization.
-
D.
serviceBranchColor
Indicates the specific color associated with a particular branch of service (e.g., military or organizational branch) as its identifying or representative color.
-
E.
isPartOfBranchTypically
Indicates that something is typically a component or subdivision within a larger 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc3219b881908a2f82126f9a679d |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.