Triple
T26731708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Mercia |
E673990
|
entity |
| Predicate | typicalTitleHolder |
P28721
|
FINISHED |
| Object | bishop |
—
|
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: bishop | Statement: [Bishop of Mercia, typicalTitleHolder, bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTitleHolder Context triple: [Bishop of Mercia, typicalTitleHolder, bishop]
-
A.
titleHolderIsUsually
chosen
Indicates that an entity serving as a title holder is typically or most commonly a particular type or category of entity.
-
B.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
C.
recognizedTitleHolder
Indicates that an entity is officially acknowledged as holding a particular title or position.
-
D.
includedTitleHolder
Indicates that an entity is recognized or recorded as holding a specified title within a given context or collection.
-
E.
titleHolderName
Indicates the name of the person or entity that holds a particular title or position.
- 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: April 27, 2026, 3:45 a.m.