Triple
T36006378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Januarius of Benevento |
E1041281
|
entity |
| Predicate | cultDevelopedAround |
P9864
|
FINISHED |
| Object | his relics |
—
|
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: his relics | Statement: [Januarius of Benevento, cultDevelopedAround, his relics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultDevelopedAround Context triple: [Januarius of Benevento, cultDevelopedAround, his relics]
-
A.
cultDevelopedInto
Indicates that one cult evolved, transformed, or was reconstituted into another cult over time.
-
B.
cultDeveloped
chosen
Indicates that a cult or devoted following has formed and grown around an entity, typically as a result of its influence, appeal, or impact.
-
C.
cultDevelopedBy
Indicates that a particular cult was created, established, or brought into being by a specific agent or entity.
-
D.
developedAround
Indicates that one entity was created, designed, or evolved with the other entity as its central focus, basis, or surrounding context.
-
E.
developedByCulture
Indicates that something (such as a practice, artifact, or idea) has been created, shaped, or brought into being through the influence or processes of a particular culture.
- 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_69f7acaffab08190abd3717d9fe857ba |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.