Triple
T13408424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syrian Turkmen |
E320019
|
entity |
| Predicate | armedGroupParticipation |
P45966
|
FINISHED |
| Object | Syrian opposition factions |
—
|
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: Syrian opposition factions | Statement: [Syrian Turkmen, armedGroupParticipation, Syrian opposition factions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedGroupParticipation Context triple: [Syrian Turkmen, armedGroupParticipation, Syrian opposition factions]
-
A.
armedGroup
Indicates that an entity is an organized group equipped with weapons and capable of using armed force.
-
B.
armedGroupInvolved
chosen
Indicates that an armed group participated in, contributed to, or was otherwise involved in the referenced event or action.
-
C.
participantGroup
Indicates a relationship in which a set or group of entities jointly participate in a common event, activity, or interaction.
-
D.
factionInvolved
Indicates that a particular faction participates in, is associated with, or plays a role in the specified event, situation, or context.
-
E.
armed
Indicates that an entity is equipped with or carrying a weapon or weapons.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbae4d2c5481908facfaaa1501e344 |
completed | April 12, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:35 p.m.