Triple
T33849900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Auki |
E867592
|
entity |
| Predicate | firstBishopStart |
P152534
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [Roman Catholic Diocese of Auki, firstBishopStart, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstBishopStart Context triple: [Roman Catholic Diocese of Auki, firstBishopStart, 1983]
-
A.
firstBishop
Indicates that one entity is the first bishop (earliest in time or rank) associated with or holding episcopal authority over another entity.
-
B.
hasFirstBishop
Indicates that an entity is associated with a specific bishop who is designated as its first bishop in a sequence or hierarchy.
-
C.
dateFirstBishopTookOffice
chosen
Indicates the calendar date on which the first bishop formally assumed office in a given jurisdiction or position.
-
D.
firstBishopConsecrated
Indicates that one entity is the first bishop to be formally consecrated in relation to another entity or context.
-
E.
dateOfFirstBishopConsecration
Indicates the calendar date on which the first bishop associated with an entity was consecrated.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:47 a.m.