Triple
T32515775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Æthelburg of Kent |
E831055
|
entity |
| Predicate | broughtClergyTo |
P143790
|
FINISHED |
| Object | Northumbria |
—
|
NE NERFINISHED |
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: Northumbria | Statement: [Æthelburg of Kent, broughtClergyTo, Northumbria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broughtClergyTo Context triple: [Æthelburg of Kent, broughtClergyTo, Northumbria]
-
A.
clergyCan
Indicates that members of the clergy are permitted or authorized to perform a specified action or exercise a particular role or function.
-
B.
clergy
Indicates that an entity serves in an official religious or spiritual leadership role within an organized faith or religious institution.
-
C.
involvesClergy
Indicates that the situation, event, or action includes the participation or presence of clergy members.
-
D.
clergyMovedTo
chosen
Indicates that a member of the clergy relocated or was transferred from one place to another.
-
E.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c4a2e4cc81909158364159fac689 |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.