Triple
T7865647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilica of Our Lady Immaculate |
E182606
|
entity |
| Predicate | elevationToBasilicaDate |
P68276
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Basilica of Our Lady Immaculate, elevationToBasilicaDate, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationToBasilicaDate Context triple: [Basilica of Our Lady Immaculate, elevationToBasilicaDate, 2014]
-
A.
elevatedToBasilica
Indicates that a church has been formally raised in status and designated as a basilica by ecclesiastical authority.
-
B.
elevationToMinorBasilica
Indicates the formal act by which a church is granted the status and title of a minor basilica within the Catholic Church.
-
C.
basilicaStatusGrantedYear
chosen
Indicates the year in which a church or religious building was officially granted the status of a basilica.
-
D.
basilicaHeightApprox
Indicates that an entity is approximately a certain height, specifically in the context of a basilica or basilica-like structure.
-
E.
elevationToAbbeyDate
Indicates the date on which an entity was formally elevated to the status of an abbey.
- 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3844eacc81908f8e1e5fc4dafec8 |
completed | March 31, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:54 p.m.