Triple
T26833797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assad family |
E675571
|
entity |
| Predicate | maintainsControlThrough |
P50835
|
FINISHED |
| Object | security apparatus |
—
|
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: security apparatus | Statement: [Assad family, maintainsControlThrough, security apparatus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainsControlThrough Context triple: [Assad family, maintainsControlThrough, security apparatus]
-
A.
exertsControlOver
Indicates that one entity has the power or authority to direct, influence, or determine the actions or decisions of another entity.
-
B.
continuesToControl
chosen
Indicates that one entity maintains ongoing authority, influence, or command over another entity or resource over time.
-
C.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
D.
canBeControlledFrom
Indicates that one entity has the ability or authority to operate, direct, or manage another entity remotely or indirectly.
-
E.
aimsToControl
Indicates an intention or effort by one entity to gain power over, direct, or regulate another entity or situation.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 5:03 a.m.