Triple
T35936742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syrian Turkmen Movement |
E1039325
|
entity |
| Predicate | politicalActivityContext |
P84578
|
FINISHED |
| Object | Syrian conflict |
—
|
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 conflict | Statement: [Syrian Turkmen Movement, politicalActivityContext, Syrian conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalActivityContext Context triple: [Syrian Turkmen Movement, politicalActivityContext, Syrian conflict]
-
A.
postPoliticalActivity
Indicates that an entity engages in political actions or activities following a particular event, period, or condition.
-
B.
politicalActivityLevel
Indicates the degree or intensity of an entity’s involvement or participation in political actions, events, or processes.
-
C.
politicalActivityStart
Indicates the point in time when an entity begins engaging in a specified political activity or role.
-
D.
politicalActivityRegion
chosen
Indicates the geographic region or area in which a political activity takes place or is focused.
-
E.
genreOfPoliticalActivity
Indicates the specific type or category of political activity that characterizes or classifies a given political action or engagement.
- 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_69f76e24bbd0819096b837d35371639a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 3, 2026, 4:07 p.m.