Triple
T30244503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spira |
E769018
|
entity |
| Predicate | hasHeritageStatusViaCathedral |
P82341
|
FINISHED |
| Object | UNESCO World Heritage Site |
—
|
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: UNESCO World Heritage Site | Statement: [Spira, hasHeritageStatusViaCathedral, UNESCO World Heritage Site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageStatusViaCathedral Context triple: [Spira, hasHeritageStatusViaCathedral, UNESCO World Heritage Site]
-
A.
heritageStatusOfCathedral
chosen
Indicates the heritage designation or protection status assigned to a cathedral.
-
B.
hasCathedralStatusAt
Indicates that an entity holds cathedral status at or during a specified time or temporal context.
-
C.
hasHistoricCathedralCity
Indicates that one entity is historically recognized as a cathedral city associated with or belonging to another entity.
-
D.
hasCathedralBasilicaStatus
Indicates that an entity (typically a church) holds the official ecclesiastical designation of a cathedral basilica.
-
E.
hasCathedralStatusSince
Indicates the point in time from which something has held the official status of a cathedral.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 29, 2026, 7:39 p.m.