Triple
T10532558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shrine of John the Baptist |
E248480
|
entity |
| Predicate | believedToContainRelicOf |
P18543
|
FINISHED |
| Object | head of 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: head of John the Baptist | Statement: [Shrine of John the Baptist, believedToContainRelicOf, head of John the Baptist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: believedToContainRelicOf Context triple: [Shrine of John the Baptist, believedToContainRelicOf, head of John the Baptist]
-
A.
containsRelic
chosen
Indicates that one entity holds, includes, or has within it a relic.
-
B.
relicBroughtBy
Indicates that a relic was transported or delivered to a location or context by a specific agent or entity.
-
C.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
-
D.
relicTraditionallyBroughtFrom
Indicates that a relic is customarily obtained or transported from a particular source or place according to tradition.
-
E.
relicDiscovery
Indicates the event or relationship in which an entity finds or uncovers a relic.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a17f23081909f3372e160e21670 |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:30 p.m.