Triple
T32993234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Begijnhof Chapel |
E844147
|
entity |
| Predicate | hasCourtyardContext |
—
|
GENERATED |
| Object | Begijnhof housing complex |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourtyardContext Context triple: [Begijnhof Chapel, hasCourtyardContext, Begijnhof housing complex]
-
A.
hasCourtyard
chosen
Indicates that one entity includes, features, or is characterized by the presence of a courtyard.
-
B.
hasCourtyardUse
Indicates that one entity is permitted or designated to use the courtyard of another entity.
-
C.
hasCourtyardFeature
Indicates that a courtyard possesses or includes a specific feature or characteristic.
-
D.
hasCourtyardArea
Indicates that an entity includes or is associated with a courtyard and specifies the size or extent of that courtyard space.
-
E.
courtyardType
Indicates the specific kind or classification of a courtyard associated with an entity.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.