Triple
T32361527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zamora Cathedral |
E826874
|
entity |
| Predicate | laterArchitecturalAdditions |
P110135
|
FINISHED |
| Object | Gothic elements |
—
|
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: Gothic elements | Statement: [Zamora Cathedral, laterArchitecturalAdditions, Gothic elements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterArchitecturalAdditions Context triple: [Zamora Cathedral, laterArchitecturalAdditions, Gothic elements]
-
A.
laterAdditionsBy
chosen
Indicates that one entity consists of or represents additions or modifications that were made to another entity at a later time.
-
B.
laterArchitecture
Indicates that one architectural style, structure, or design chronologically follows and is influenced by another.
-
C.
hasArchitecturalModificationType
Indicates that an entity has undergone a specific type or category of architectural modification.
-
D.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
E.
laterBuiltOverBy
Indicates that a structure or feature was constructed at a later time on top of, or replacing, an earlier one.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
Created at: May 1, 2026, 12:49 a.m.