Triple
T31077035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theuderic II |
E791993
|
entity |
| Predicate | notableEcclesiasticalContact |
P207342
|
FINISHED |
| Object | Columbanus of Luxeuil |
E223925
|
NE 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: Columbanus of Luxeuil | Statement: [Theuderic II, notableEcclesiasticalContact, Columbanus of Luxeuil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEcclesiasticalContact Context triple: [Theuderic II, notableEcclesiasticalContact, Columbanus of Luxeuil]
-
A.
addressesChurch
Indicates that one entity delivers a speech, message, or communication specifically directed to a church or church congregation.
-
B.
clergySystem
Indicates a relationship in which an organized religious institution or tradition has a structured system of clergy roles, ranks, or offices.
-
C.
clergyIncardination
Indicates that a member of the clergy is formally attached or assigned to a particular diocese, religious institute, or ecclesiastical jurisdiction.
-
D.
ecclesiasticalRole
Indicates that one entity holds or is assigned a specific religious or church-related office, function, or position in relation to another entity.
-
E.
notableExplorerContact
Indicates that an entity has had a significant interaction or encounter with a well-known explorer.
- F. None of above. chosen
Provenance (5 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b8493e1b88190ac18f5ace044832b |
completed | June 12, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:02 p.m.