Triple
T31468944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compostelan Holy Year |
E802799
|
entity |
| Predicate | HolyDoorOpeningDate |
P10845
|
FINISHED |
| Object | Evening of 31 December preceding the Holy Year |
—
|
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: Evening of 31 December preceding the Holy Year | Statement: [Compostelan Holy Year, HolyDoorOpeningDate, Evening of 31 December preceding the Holy Year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HolyDoorOpeningDate Context triple: [Compostelan Holy Year, HolyDoorOpeningDate, Evening of 31 December preceding the Holy Year]
-
A.
HolyDoorOpeningBy
Indicates that a holy door is opened through the action or authority of a specified agent.
-
B.
bronzeDoorsDate
Indicates the date or time period associated with the creation, installation, or use of the bronze doors.
-
C.
mainPortalDate
Indicates the primary or official date associated with a portal’s main event, status, or activation.
-
D.
rerAOpeningDate
Indicates the date on which something (such as a facility, service, or route) is opened again after having been closed.
-
E.
officialOpeningDate
chosen
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 9:25 p.m.