Triple
T10044892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathédrale Sainte-Marie de Bayonne |
E207589
|
entity |
| Predicate | hasCloisterFrom |
P65756
|
FINISHED |
| Object | 13th century |
—
|
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: 13th century | Statement: [Cathédrale Sainte-Marie de Bayonne, hasCloisterFrom, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCloisterFrom Context triple: [Cathédrale Sainte-Marie de Bayonne, hasCloisterFrom, 13th century]
-
A.
hasCloister
Indicates that one entity possesses or includes a cloister as part of its structure or layout.
-
B.
hasCloisterFromCentury
chosen
Indicates that an entity possesses a cloister that dates from, or was constructed in, a specified century.
-
C.
cloisterStyle
Indicates the architectural style or design characteristics of a cloister in relation to a building or site.
-
D.
cloisterConstruction
Indicates the construction or building activity specifically related to a cloister or cloistered architectural space.
-
E.
hasSacristy
Indicates that a religious building includes or is associated with a sacristy (a room where sacred vessels, vestments, and liturgical items are kept and prepared).
- 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf62ecf081909c055171b78a883a |
completed | April 2, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:56 p.m.