Triple
T22606830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teruel Cathedral |
E566582
|
entity |
| Predicate | roofDecorationDate |
P148905
|
FINISHED |
| Object | 14th 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: 14th century | Statement: [Teruel Cathedral, roofDecorationDate, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roofDecorationDate Context triple: [Teruel Cathedral, roofDecorationDate, 14th century]
-
A.
renovatedAfter
Indicates that one entity was renovated at a later time than another entity.
-
B.
constructionDate
Indicates the date on which an entity (such as a building or structure) was constructed or completed.
-
C.
claimedConstructionDate
Indicates the date on which an entity is asserted or reported to have been constructed, according to some claim or source.
-
D.
hasCeilingDecoration
Indicates that an entity features or is adorned with a decorative element on its ceiling.
-
E.
associatedBuildingDate
Indicates the date on which a particular building is formally linked or related to another entity or record.
- 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_69e245884860819081046ce07d5872c4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1627172488190beb87df965498bcc |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 2:54 p.m.