Triple
T30603549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quwwāt Sūriyā al-Dīmuqrāṭīya |
E778974
|
entity |
| Predicate | hasAllegedFormationYear |
P184005
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Quwwāt Sūriyā al-Dīmuqrāṭīya, hasAllegedFormationYear, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAllegedFormationYear Context triple: [Quwwāt Sūriyā al-Dīmuqrāṭīya, hasAllegedFormationYear, 2015]
-
A.
monthOfFormation
Indicates the specific calendar month in which an entity (such as an organization or group) was formally established or created.
-
B.
hasYearOfEstablishment
Indicates the specific year in which an entity was founded, created, or formally established.
-
C.
establishedAt
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
D.
formedInYear
Indicates the year in which an entity was originally established, created, or came into existence.
-
E.
underlyingCompanyFormationYear
Indicates the calendar year in which the referenced underlying company was originally formed or established.
- F. None of above. chosen
Provenance (4 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_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: April 29, 2026, 8:25 p.m.