Triple
T17495790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albi Cathedral |
E426055
|
entity |
| Predicate | interiorDecorationPeriod |
P9594
|
FINISHED |
| Object | 15th 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: 15th century | Statement: [Albi Cathedral, interiorDecorationPeriod, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interiorDecorationPeriod Context triple: [Albi Cathedral, interiorDecorationPeriod, 15th century]
-
A.
interiorDecoratedBy
Indicates that the interior of a space or structure has been designed or decorated by a specific agent or entity.
-
B.
culturalPeriod
chosen
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
C.
interiorStyle
Indicates that one entity has a particular interior design style or aesthetic characterized by the other entity.
-
D.
hasRichInteriorDecoration
Indicates that an entity features elaborate, ornate, or luxuriously detailed interior decoration.
-
E.
designPeriod
Indicates the time span during which something is planned, designed, or conceptually developed before implementation or production.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4520dd9508190872a71d3722228e2 |
completed | April 19, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.