Triple
T26566401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of San Cristóbal de La Laguna |
E666395
|
entity |
| Predicate | episcopalSeeCreated |
P132442
|
FINISHED |
| Object | 1819 |
—
|
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: 1819 | Statement: [Bishop of San Cristóbal de La Laguna, episcopalSeeCreated, 1819]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: episcopalSeeCreated Context triple: [Bishop of San Cristóbal de La Laguna, episcopalSeeCreated, 1819]
-
A.
episcopalSeeOf
Indicates that one entity serves as the episcopal see (the official seat or jurisdictional center) of a bishop or similar ecclesiastical authority for another entity.
-
B.
episcopalSeeTransferredTo
Indicates that the authority or jurisdiction of a bishop’s episcopal see has been officially moved from one location or diocese to another.
-
C.
dioceseEstablishedBy
Indicates that a diocese was founded, created, or formally instituted by a particular person or authority.
-
D.
dioceseErectedOn
chosen
Indicates the date or point in time when a diocese was formally established or created.
-
E.
bishopricCreated
Indicates that a bishopric (an ecclesiastical jurisdiction or office of a bishop) has been formally established or created.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6149f29c88190b4899c61a28828c1 |
completed | May 2, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:55 a.m.