Triple
T19740385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genoa Cathedral |
E474098
|
entity |
| Predicate | relicContained |
P18543
|
FINISHED |
| Object | relics of Saint John the Baptist |
—
|
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: relics of Saint John the Baptist | Statement: [Genoa Cathedral, relicContained, relics of Saint John the Baptist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relicContained Context triple: [Genoa Cathedral, relicContained, relics of Saint John the Baptist]
-
A.
containsRelic
chosen
Indicates that one entity holds, includes, or has within it a relic.
-
B.
relicDiscovery
Indicates the event or relationship in which an entity finds or uncovers a relic.
-
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.
relicsLocatedIn
Indicates that certain relics are situated, stored, or found within a specific location.
-
E.
relicBroughtBy
Indicates that a relic was transported or delivered to a location or context by a specific agent or entity.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6516159c8819090022094aa91902b |
completed | April 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.