Triple
T30818889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | بلاد الشام |
E784861
|
entity |
| Predicate | عاصمة_تاريخية_رئيسية |
P3417
|
FINISHED |
| Object | دمشق |
—
|
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: دمشق | Statement: [بلاد الشام, عاصمة_تاريخية_رئيسية, دمشق]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: عاصمة_تاريخية_رئيسية Context triple: [بلاد الشام, عاصمة_تاريخية_رئيسية, دمشق]
-
A.
formerCapitalOf
chosen
Indicates that a place once served as the capital of another entity (such as a country or region) but no longer holds that status.
-
B.
historicalCapitalNow
Indicates that a location currently serves as the capital of an entity for which it also held capital status at some point in the past.
-
C.
capitalOfRuledEntity
Indicates that a city or settlement serves as the capital of a political entity that rules or governs another entity.
-
D.
capitalLocation
Indicates the relationship in which a place serves as the capital city or administrative center of a given political or geographic entity.
-
E.
servedAsNationalCapitalFrom
Indicates that a place functioned as the national capital of a country or political entity during a specified time period.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6906ad50481909a700664e0b70fb0 |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:44 p.m.