Triple
T27830291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctus Iacobus |
E703074
|
entity |
| Predicate | martyrdomDateTradition |
P163390
|
FINISHED |
| Object | circa 44 CE |
—
|
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: circa 44 CE | Statement: [Sanctus Iacobus, martyrdomDateTradition, circa 44 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: martyrdomDateTradition Context triple: [Sanctus Iacobus, martyrdomDateTradition, circa 44 CE]
-
A.
traditionallyMartyredWith
Indicates that an entity is customarily believed or depicted to have been martyred using a particular method, instrument, or circumstance.
-
B.
sharesMartyrdomTraditionWith
Indicates that two entities are connected by a common or closely related tradition, narrative, or veneration surrounding martyrdom.
-
C.
martyrAssociated
Indicates that there is a relationship of connection or involvement between an entity and a martyr, such as affiliation, support, or commemoration.
-
D.
traditionalMartyrdomSiteOf
Indicates that a place is traditionally regarded as the location where a particular individual was martyred.
-
E.
martyrdomStatus
Indicates the state or condition of an entity with respect to being recognized or regarded as a martyr.
- F. None of above. chosen
Provenance (4 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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6389b1a308190980360ec13e19549 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 5:55 p.m.