Triple
T20598159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope Anacletus |
E506103
|
entity |
| Predicate | traditionallyDiedAs |
P135909
|
FINISHED |
| Object | martyr |
—
|
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: martyr | Statement: [Pope Anacletus, traditionallyDiedAs, martyr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyDiedAs Context triple: [Pope Anacletus, traditionallyDiedAs, martyr]
-
A.
traditionallyDiedIn
Indicates that, according to tradition or customary accounts (rather than strictly verified historical evidence), one entity is said to have died in the location or context of another entity.
-
B.
traditionallyDied
chosen
Indicates that an entity died in the manner, context, or circumstances specified by a particular tradition or customary account.
-
C.
traditionalMannerOfDeath
Indicates that an entity died in a way that follows or reflects a culturally recognized or customary method of death.
-
D.
diedAs
Indicates that an entity ceased to live in a particular role, state, or identity.
-
E.
traditionallyMartyredWith
Indicates that an entity is customarily believed or depicted to have been martyred using a particular method, instrument, or circumstance.
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1d15b08190a720fc7cefbf333e |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.