Triple
T29723855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lac Region |
E752125
|
entity |
| Predicate | hasSecurityActor |
P22957
|
FINISHED |
| Object | Chadian armed forces |
—
|
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: Chadian armed forces | Statement: [Lac Region, hasSecurityActor, Chadian armed forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityActor Context triple: [Lac Region, hasSecurityActor, Chadian armed forces]
-
A.
hasPrimarySecurityActor
Indicates that an entity is associated with, or overseen by, the main organization or individual responsible for its security functions or protection.
-
B.
hasSecurityAuthority
Indicates that one entity possesses the right or power to enforce, manage, or make decisions about security over another entity or resource.
-
C.
hasSecurityPresence
chosen
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
D.
hasSafetyRole
Indicates that an entity holds a responsibility or function related to safety within a given context or system.
-
E.
hasSecurityArea
Indicates that an entity is associated with, assigned to, or falls within a defined security-controlled area or zone.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: April 28, 2026, 7:38 p.m.