Triple
T5003964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloître Saint-André-le-Bas |
E112440
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romanesque architectural site |
C13234
|
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: Romanesque architectural site Context triple: [Cloître Saint-André-le-Bas, instanceOf, Romanesque architectural site]
-
A.
Romanesque church building
chosen
A Romanesque church building is a medieval Christian structure characterized by thick stone walls, rounded arches, sturdy piers, small windows, and a fortress-like, monumental appearance.
-
B.
Manueline architectural monument
A Manueline architectural monument is a grand structure exemplifying the ornate, late-Gothic Portuguese style characterized by intricate maritime, religious, and royal symbolism carved into stone.
-
C.
reconstructed historic site
A reconstructed historic site is a place where buildings, structures, or environments from the past have been rebuilt or significantly restored to approximate their original appearance and context for educational, commemorative, or touristic purposes.
-
D.
Romanesque Revival building
A Romanesque Revival building is a structure designed in a 19th-century historicist style that reinterprets medieval Romanesque architecture through features like round arches, heavy masonry, robust towers, and deeply recessed openings.
-
E.
Historic site
A historic site is a location of significant past events, structures, or cultural heritage that is preserved and recognized for its historical importance.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:35 p.m.