Triple
T38363118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Vibiana |
E892349
|
entity |
| Predicate | relicsPreviouslyLocatedIn |
P36131
|
FINISHED |
| Object | Cathedral of Saint Vibiana |
—
|
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: Cathedral of Saint Vibiana | Statement: [Saint Vibiana, relicsPreviouslyLocatedIn, Cathedral of Saint Vibiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relicsPreviouslyLocatedIn Context triple: [Saint Vibiana, relicsPreviouslyLocatedIn, Cathedral of Saint Vibiana]
-
A.
relicsLocatedIn
chosen
Indicates that certain relics are situated, stored, or found within a specific location.
-
B.
relicsDiscoveryYear
Indicates the year in which the relics were discovered.
-
C.
relicsAssociatedWith
Indicates a relationship where certain relics are connected or linked to a particular entity, context, or subject (such as a person, place, event, or tradition).
-
D.
relicDiscovery
Indicates the event or relationship in which an entity finds or uncovers a relic.
-
E.
relicTraditionallyBroughtFrom
Indicates that a relic is customarily obtained or transported from a particular source or place according to tradition.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcc7a4d7f881908b43b960911b81e9 |
completed | May 7, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69fcc589720c819089c8f500fea3c86a |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:31 p.m.