Triple
T13214701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haarlemse Hofjes |
E314580
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic courtyard complex |
C6351
|
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: historic courtyard complex Context triple: [Haarlemse Hofjes, instanceOf, historic courtyard complex]
-
A.
historic courtyard
chosen
A historic courtyard is an open, often enclosed outdoor space surrounded by buildings or walls that reflects the architectural, cultural, and social practices of a particular past era.
-
B.
historic city square
A historic city square is a central public open space in a town or city, typically surrounded by significant buildings and monuments, that has served as a focal point for social, political, and commercial activities over time.
-
C.
ancient guesthouse complex
An ancient guesthouse complex is a historical lodging facility composed of multiple interconnected structures and courtyards designed to accommodate travelers, provide communal services, and support trade or pilgrimage along important routes.
-
D.
historic garden
A historic garden is a designed outdoor space of recognized cultural, aesthetic, or historical significance, preserved or restored to reflect the landscape styles, plantings, and features of a particular period or tradition.
-
E.
historic estate
A historic estate is a large, significant property—often including a grand residence, outbuildings, and landscaped grounds—that holds cultural, architectural, or historical importance from a past era.
- F. None of above.
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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:18 p.m.