Triple
T6597969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosel |
E148522
|
entity |
| Predicate | appointedAsBishopInCentury |
P71970
|
FINISHED |
| Object | 7th century |
—
|
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: 7th century | Statement: [Bosel, appointedAsBishopInCentury, 7th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsBishopInCentury Context triple: [Bosel, appointedAsBishopInCentury, 7th century]
-
A.
dateOfFirstBishopConsecration
Indicates the calendar date on which the first bishop associated with an entity was consecrated.
-
B.
appointedBishopOf
Indicates that a person has been officially assigned or consecrated to serve as the bishop responsible for a particular diocese or ecclesiastical jurisdiction.
-
C.
consecratedAsBishopIn
Indicates that a person was formally ordained and installed as a bishop within a specified place, diocese, or jurisdiction.
-
D.
affirmedInCentury
Indicates that a statement, belief, or status was formally confirmed or upheld during a specified century.
-
E.
currentArchbishopStartYear
Indicates the calendar year in which the current archbishop began serving in that role.
- 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_69c687e7b8688190811ffee72e096468 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acfd17388190bd0bb8b2371e7df1 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 1:56 p.m.