Triple
T3257707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monastery of San Juan de los Reyes |
E68335
|
entity |
| Predicate | cloisterStyle |
P46915
|
FINISHED |
| Object | late Gothic |
—
|
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: late Gothic | Statement: [Monastery of San Juan de los Reyes, cloisterStyle, late Gothic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cloisterStyle Context triple: [Monastery of San Juan de los Reyes, cloisterStyle, late Gothic]
-
A.
hasCloister
Indicates that one entity possesses or includes a cloister as part of its structure or layout.
-
B.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
-
C.
monasteryType
Indicates the specific kind or classification of a monastery in relation to its broader religious or organizational category.
-
D.
cathedral
Indicates that an entity is a cathedral, i.e., it has the status or function of a principal church, typically one that is the seat of a bishop.
-
E.
ecclesiasticalStyle
Indicates the formal religious or clerical style or title by which an ecclesiastical person is properly addressed.
- F. None of above. chosen
Provenance (4 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf6a46448190a7fa0ca83fa096f8 |
completed | March 8, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:09 p.m.