Triple
T36006286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feast of Saint Januarius |
E1041279
|
entity |
| Predicate | associatedRelic |
P132165
|
FINISHED |
| Object | blood of Saint Januarius |
—
|
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: blood of Saint Januarius | Statement: [Feast of Saint Januarius, associatedRelic, blood of Saint Januarius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRelic Context triple: [Feast of Saint Januarius, associatedRelic, blood of Saint Januarius]
-
A.
containsRelic
Indicates that one entity holds, includes, or has within it a relic.
-
B.
relicsAssociatedWith
chosen
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).
-
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.
relicBroughtBy
Indicates that a relic was transported or delivered to a location or context by a specific agent or entity.
-
E.
numberOfRelics
Indicates the quantitative count of relics associated with a given entity or context.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.