Triple
T9020531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilica of the Holy Blood |
E215710
|
entity |
| Predicate | lowerChapelStyle |
P57617
|
FINISHED |
| Object | Romanesque architecture |
—
|
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: Romanesque architecture | Statement: [Basilica of the Holy Blood, lowerChapelStyle, Romanesque architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerChapelStyle Context triple: [Basilica of the Holy Blood, lowerChapelStyle, Romanesque architecture]
-
A.
hasChapelStyle
chosen
Indicates that a chapel possesses or is characterized by a particular architectural or stylistic design.
-
B.
chamberLower
Indicates that the entity serves as the lower chamber (e.g., house) within a bicameral or multi-chamber legislative or decision-making body.
-
C.
cloisterStyle
Indicates the architectural style or design characteristics of a cloister in relation to a building or site.
-
D.
lowerStage
Indicates that one entity is at a lower or earlier stage, level, or phase in a progression or hierarchy than another entity.
-
E.
lowerLocation
Indicates that one entity is located physically below or at a lower vertical position relative to another entity.
- 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_69ca83a38aa88190bf1bb80c4548b5e2 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a421c2c8190abb12c826066fe75 |
completed | April 1, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.