Triple
T5622195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Syria |
E147632
|
entity |
| Predicate | roleInSyrianCivilWar |
P6060
|
FINISHED |
| Object | major theater of 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: major theater of conflict | Statement: [Western Syria, roleInSyrianCivilWar, major theater of conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSyrianCivilWar Context triple: [Western Syria, roleInSyrianCivilWar, major theater of conflict]
-
A.
legalStatusInSyria
Indicates the legal status or condition an entity holds under the laws and regulations of Syria.
-
B.
roleInIsrael
Indicates that an entity holds or held a specific role, position, or function within the context of Israel.
-
C.
conflictSide
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
D.
conflictRole
chosen
Indicates that an entity plays a specific role or position within a conflict or dispute between parties.
-
E.
regionOfConflict
Indicates that a specified region is the location where a particular conflict or dispute takes place.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c022133eec819086acb04864dde5ee |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.