Triple
T7568445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alawites |
E179178
|
entity |
| Predicate | civilWarContext |
P70835
|
FINISHED |
| Object | key support base for Syrian government in Syrian civil war |
—
|
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: key support base for Syrian government in Syrian civil war | Statement: [Alawites, civilWarContext, key support base for Syrian government in Syrian civil war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilWarContext Context triple: [Alawites, civilWarContext, key support base for Syrian government in Syrian civil war]
-
A.
civilWarPeriod
Indicates a time span during which a civil war is occurring or in effect.
-
B.
civilWarSignificance
chosen
Indicates the importance or impact that a particular entity, event, or factor has within the context of a civil war.
-
C.
civilWarStart
Indicates the point in time or event at which an internal armed conflict between factions of the same state or society begins.
-
D.
civilWarEnd
Indicates that an internal armed conflict within a country has come to an official or de facto conclusion.
-
E.
従軍紛争
Indicates participation in or involvement with a military conflict or war.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f91d9bfc8190af6f5f8211c3dda2 |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.