Triple
T22117980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Andrew’s Cathedral |
E546589
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national monument of Singapore |
C45824
|
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: national monument of Singapore Context triple: [St Andrew’s Cathedral, instanceOf, national monument of Singapore]
-
A.
national monument of the Netherlands
A national monument of the Netherlands is a building, structure, or site officially designated and protected by the Dutch government for its exceptional cultural, historical, or architectural significance.
-
B.
Angkor monument
An Angkor monument is a large-scale architectural and sculptural structure from the Angkor civilization, typically serving religious, ceremonial, or commemorative functions within the Khmer Empire’s temple complexes.
-
C.
United States National Monument
A United States National Monument is a protected area designated by the federal government, typically by presidential proclamation, to preserve significant natural, cultural, historical, or scientific features.
-
D.
national city park
A national city park is a protected natural or landscaped area within or adjacent to an urban environment, designated and managed at the national level to conserve biodiversity, provide recreation, and enhance residents’ quality of life.
-
E.
national monument of Portugal
A national monument of Portugal is a culturally, historically, or architecturally significant site, building, or structure officially designated and protected by the Portuguese state as part of the nation’s heritage.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:31 p.m.