Triple
T7568442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alawites |
E179178
|
entity |
| Predicate | integrationInSyria |
P43037
|
FINISHED |
| Object | increased under French Mandate |
—
|
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: increased under French Mandate | Statement: [Alawites, integrationInSyria, increased under French Mandate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integrationInSyria Context triple: [Alawites, integrationInSyria, increased under French Mandate]
-
A.
readmissionOfSyria
Indicates the action or event of Syria being allowed to rejoin or be reinstated into a group, organization, or body from which it was previously excluded.
-
B.
legalStatusInSyria
chosen
Indicates the legal status or condition an entity holds under the laws and regulations of Syria.
-
C.
lostLastTerritoryInSyria
Indicates that the entity ceased to control its final remaining territorial holding within Syria.
-
D.
distanceFromSyriaBorder
Indicates the measured spatial separation between a location and the nearest point on Syria’s national border.
-
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_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.