Triple
T32732859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mardin Ridge |
E836999
|
entity |
| Predicate | isBackdropOf |
P26195
|
FINISHED |
| Object | Mardin cityscape |
—
|
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: Mardin cityscape | Statement: [Mardin Ridge, isBackdropOf, Mardin cityscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBackdropOf Context triple: [Mardin Ridge, isBackdropOf, Mardin cityscape]
-
A.
formsBackdropOf
chosen
Indicates that one entity serves as the background or setting against which another entity is viewed, occurs, or is presented.
-
B.
primaryBackdropFor
Indicates that one entity serves as the main visual or contextual background element for another entity.
-
C.
isBehind
Indicates that one entity is positioned to the rear of another entity along a relevant spatial or directional axis.
-
D.
reflectsBackgroundIn
Indicates that one entity’s surface or appearance shows a visible image or likeness of another entity situated behind it.
-
E.
locatedBehind
Indicates that one entity is positioned at the rear of or on the far side of another entity along a given viewing or reference direction.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c90238dc8190b8e720febc017c7a |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f717a88190a924d614c2c9bca3 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:11 a.m.