Triple
T35520081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Division |
E1026527
|
entity |
| Predicate | engagesTarget |
P183198
|
FINISHED |
| Object | insurgent groups |
—
|
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: insurgent groups | Statement: [Golden Division, engagesTarget, insurgent groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagesTarget Context triple: [Golden Division, engagesTarget, insurgent groups]
-
A.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
B.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
C.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
-
D.
seeksEngagementWith
Indicates an entity’s active effort or intention to initiate or maintain interaction, involvement, or responsive connection with another entity.
-
E.
engagedBy
Indicates that an entity is actively involved, occupied, or participating in an activity, process, or interaction initiated or provided by another entity.
- F. None of above. chosen
Provenance (4 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79a53ccc481908421ae16e69aa8a4 |
completed | May 3, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:04 p.m.