Triple
T37699846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral of St. Mary the Crowned, Gibraltar |
E939028
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | landmark in Gibraltar |
C65590
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: landmark in Gibraltar Context triple: [Cathedral of St. Mary the Crowned, Gibraltar, instanceOf, landmark in Gibraltar]
-
A.
landmark in London
A landmark in London is a notable and recognizable physical site or structure within the city that holds historical, cultural, architectural, or social significance and serves as a point of reference for residents and visitors.
-
B.
landmark in Bristol
A landmark in Bristol is a notable physical feature, building, or site within the city that is widely recognized for its historical, cultural, architectural, or social significance and serves as a key point of reference or attraction.
-
C.
landmark in Jerusalem
A landmark in Jerusalem is a notable physical site or structure within the city that holds historical, religious, cultural, or architectural significance and serves as a recognizable point of reference for locals and visitors.
-
D.
landmark in Bastion
A landmark in Bastion is a notable, named location or structure within the Bastion world that serves as a recognizable point of interest for navigation, story events, or player interaction.
-
E.
symbol of Cádiz
The symbol of Cádiz is a heraldic emblem featuring a crowned shield with a castle, a lion, and maritime elements that represent the city's historical significance as a fortified port and gateway between the Atlantic and the Mediterranean.
- F. None of above. chosen
Provenance (1 batch)
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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.