Triple
T31468943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compostelan Holy Year |
E802799
|
entity |
| Predicate | HolyDoorOpeningBy |
P172248
|
FINISHED |
| Object | Archbishop of Santiago de Compostela |
—
|
NE NERFINISHED |
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: Archbishop of Santiago de Compostela | Statement: [Compostelan Holy Year, HolyDoorOpeningBy, Archbishop of Santiago de Compostela]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HolyDoorOpeningBy Context triple: [Compostelan Holy Year, HolyDoorOpeningBy, Archbishop of Santiago de Compostela]
-
A.
doorSymbol
Indicates a symbolic representation that denotes or marks the presence or concept of a door.
-
B.
doorwayFeature
Indicates that one entity is a feature, characteristic, or structural element specifically associated with a doorway of another entity.
-
C.
homeHallOpened
Indicates that a hall or corridor within a home has been opened, such as by unlocking or opening an access point.
-
D.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
-
E.
hasStageDoor
Indicates that a venue or building possesses a dedicated stage door used for performers and staff to access backstage areas.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 30, 2026, 9:25 p.m.