Triple
T26833804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assad family |
E675571
|
entity |
| Predicate | securityFigure |
P168580
|
FINISHED |
| Object | Maher al-Assad |
—
|
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: Maher al-Assad | Statement: [Assad family, securityFigure, Maher al-Assad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityFigure Context triple: [Assad family, securityFigure, Maher al-Assad]
-
A.
securityFeature
Indicates that an entity provides, embodies, or is associated with a mechanism or property intended to enhance safety, protection, or defense against threats or vulnerabilities.
-
B.
securityArrangements
Indicates the existence, nature, or details of protective measures or safeguards established between or around entities.
-
C.
security
Indicates that an entity provides protection, safety measures, or safeguards to another entity or against specific threats or risks.
-
D.
securityInstrument
Indicates that one entity serves as a security instrument (such as collateral or a guarantee) in relation to another entity or obligation.
-
E.
securityPillar
Indicates that one entity functions as a foundational security pillar or core security domain in relation to 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 27, 2026, 5:03 a.m.