Triple
T38558672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Church |
E925314
|
entity |
| Predicate | majorBasilica |
P72529
|
FINISHED |
| Object | St. Peter's Basilica |
—
|
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: St. Peter's Basilica | Statement: [Roman Church, majorBasilica, St. Peter's Basilica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorBasilica Context triple: [Roman Church, majorBasilica, St. Peter's Basilica]
-
A.
majorBasilicaOf
chosen
Indicates that one entity is designated as a major basilica associated with, located in, or belonging to another entity (typically a city, region, or religious jurisdiction).
-
B.
otherMajorBasilica
Indicates that one basilica stands in a specified relationship as an “other” major basilica to another, distinguishing it from a primary or reference major basilica.
-
C.
hasBasilicaRank
Indicates that an entity holds the ecclesiastical status or designation of a basilica within a religious hierarchy.
-
D.
basilicaStyle
Indicates that something is designed, built, or characterized in the architectural style of a basilica.
-
E.
hasBasilica
Indicates that one entity possesses, contains, or is associated with a basilica as a significant feature or component.
- 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0056174c908190be99c91a70393e47 |
completed | May 10, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_6a00538e7e08819091ecd4316cd641a1 |
completed | May 10, 2026, 9:44 a.m. |
Created at: May 3, 2026, 4:32 p.m.