Triple
T34278153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bab Sharqi |
E879518
|
entity |
| Predicate | isHistoricEntranceTo |
P39341
|
FINISHED |
| Object | ancient city of Damascus |
—
|
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: ancient city of Damascus | Statement: [Bab Sharqi, isHistoricEntranceTo, ancient city of Damascus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricEntranceTo Context triple: [Bab Sharqi, isHistoricEntranceTo, ancient city of Damascus]
-
A.
hasHistoricGate
chosen
Indicates that an entity possesses or is associated with a historically significant gate or gateway structure.
-
B.
isHistoricFor
Indicates that something has historical significance, relevance, or impact specifically in relation to a given entity or context.
-
C.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
D.
isHistoricCrossing
Indicates that a crossing between two locations has historical significance, such as being notable in history, heritage, or past events.
-
E.
isInHistoricRegister
Indicates that an entity has been officially listed or recorded in a recognized historic register or registry.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.