Triple
T30603538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quwwāt Sūriyā al-Dīmuqrāṭīya |
E778974
|
entity |
| Predicate | hasChristianComponent |
P181375
|
FINISHED |
| Object | Syriac Military Council |
—
|
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: Syriac Military Council | Statement: [Quwwāt Sūriyā al-Dīmuqrāṭīya, hasChristianComponent, Syriac Military Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChristianComponent Context triple: [Quwwāt Sūriyā al-Dīmuqrāṭīya, hasChristianComponent, Syriac Military Council]
-
A.
hasChristianCommunity
Indicates that a place or entity possesses or hosts an established Christian community.
-
B.
hasMajorChristianDenomination
Indicates that an entity (typically a religion, region, or population) includes or is associated with a principal branch or major denomination of Christianity.
-
C.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
D.
hasTheologicalElement
chosen
Indicates that something includes, expresses, or is characterized by a theological aspect, theme, or component.
-
E.
isChristianChurch
Indicates that the subject is a church that follows or is affiliated with the Christian religion.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 29, 2026, 8:25 p.m.