Triple
T26731704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Mercia |
E673990
|
entity |
| Predicate | seatInPoliticalSystem |
P161177
|
FINISHED |
| Object | Mercian kingdom |
—
|
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: Mercian kingdom | Statement: [Bishop of Mercia, seatInPoliticalSystem, Mercian kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatInPoliticalSystem Context triple: [Bishop of Mercia, seatInPoliticalSystem, Mercian kingdom]
-
A.
seatInGovernment
Indicates that an entity holds an official position or membership within a governmental body or institution.
-
B.
seatInGovernmentHierarchy
Indicates that an entity holds a specific position or rank within a structured governmental hierarchy.
-
C.
seatOfRepresentative
Indicates the location or institution where a representative officially holds their position or exercises their duties.
-
D.
governsInPoliticalSystem
Indicates that one entity exercises authoritative control or rule over another entity within a specified political system or structure.
-
E.
partySystemRole
Indicates the specific functional role or capacity that a party assumes within a given system or context.
- 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61841b5bc8190a3048c5cca7849a7 |
completed | May 2, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f6106d346c8190868489f36c65b6ec |
completed | May 2, 2026, 2:55 p.m. |
Created at: April 27, 2026, 3:45 a.m.