Triple
T13503505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Philomena’s Cathedral |
E320949
|
entity |
| Predicate | hasAltarRelic |
P18543
|
FINISHED |
| Object | relic of Saint Philomena |
—
|
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: relic of Saint Philomena | Statement: [St. Philomena’s Cathedral, hasAltarRelic, relic of Saint Philomena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAltarRelic Context triple: [St. Philomena’s Cathedral, hasAltarRelic, relic of Saint Philomena]
-
A.
hasAltar
Indicates that one entity possesses, contains, or includes an altar as part of its features or components.
-
B.
hasAltarLocation
Indicates that an altar is situated at or associated with a specific location.
-
C.
hasAltarType
Indicates that an entity is associated with or characterized by a specific type or category of altar.
-
D.
containsRelic
chosen
Indicates that one entity holds, includes, or has within it a relic.
-
E.
hasRelicsStatus
Indicates that an entity holds a particular status or condition specifically related to relics.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf810e248190a060481004503f96 |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.