Triple
T1237425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James the brother of Jesus |
E26578
|
entity |
| Predicate | martyrdomTradition |
P13958
|
FINISHED |
| Object | executed in Jerusalem |
—
|
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: executed in Jerusalem | Statement: [James the brother of Jesus, martyrdomTradition, executed in Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: martyrdomTradition Context triple: [James the brother of Jesus, martyrdomTradition, executed in Jerusalem]
-
A.
martyrdomStatus
Indicates the state or condition of an entity with respect to being recognized or regarded as a martyr.
-
B.
traditionAscribes
chosen
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
-
C.
theologicalTradition
Indicates the religious or doctrinal school, lineage, or system of belief within which an entity’s theology is developed or practiced.
-
D.
methodOfPersecution
Indicates the specific means, technique, or process by which an act of persecution is carried out.
-
E.
liturgicalTradition
Indicates the specific religious rite or ceremonial tradition according to which a worship service, practice, or community operates.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf3f07c08190a402e8341c1f38cc |
completed | March 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69a4bb67d52c8190815d6356b79d6ed5 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.