Triple
T25377964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | African Standby Force |
E633103
|
entity |
| Predicate | regionalBrigade |
P35496
|
FINISHED |
| Object | North African Regional Standby Brigade |
—
|
NE NERFINISHED |
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: North African Regional Standby Brigade | Statement: [African Standby Force, regionalBrigade, North African Regional Standby Brigade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalBrigade Context triple: [African Standby Force, regionalBrigade, North African Regional Standby Brigade]
-
A.
brigade
chosen
Indicates that one entity is organized as, belongs to, or is associated with a military or paramilitary brigade in relation to another entity.
-
B.
regimentalGroup
Indicates that one entity is organized as, or belongs to, a specific regimental-level military group in relation to another entity.
-
C.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
-
D.
battleGroup
Indicates that multiple military units or forces are organized together as a single coordinated combat formation.
-
E.
guardRegiment
Indicates that one entity serves as a protective or security regiment for another 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 21, 2026, 1:38 p.m.