Triple
T11496374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liturgy of St. James |
E272544
|
entity |
| Predicate | roleOfJamesTheJust |
P99805
|
FINISHED |
| Object | first bishop of 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: first bishop of Jerusalem | Statement: [Liturgy of St. James, roleOfJamesTheJust, first bishop of Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfJamesTheJust Context triple: [Liturgy of St. James, roleOfJamesTheJust, first bishop of Jerusalem]
-
A.
roleOfJulian
Indicates the specific role, function, or position that Julian holds in relation to another entity or context.
-
B.
JacobiteLeader
Indicates that a person holds a leadership role within the Jacobite movement or cause.
-
C.
firstRuledScotlandFrom
Indicates the location or domain from which an entity first exercised ruling authority over Scotland.
-
D.
dynasticReligionRole
Indicates a relationship where an entity holds a religious office, function, or status specifically within the context of a ruling dynasty or hereditary line.
-
E.
firstLordProtector
Indicates that the subject is the first individual to hold the position or title of Lord Protector in relation to the object.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85de183f08190abfa36eaabc61dc6 |
completed | April 10, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.