Triple
T34062732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Oakland |
E873535
|
entity |
| Predicate | previousCathedral |
P22831
|
FINISHED |
| Object | Cathedral of Saint Francis de Sales |
—
|
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: Cathedral of Saint Francis de Sales | Statement: [Diocese of Oakland, previousCathedral, Cathedral of Saint Francis de Sales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousCathedral Context triple: [Diocese of Oakland, previousCathedral, Cathedral of Saint Francis de Sales]
-
A.
formerCathedral
chosen
Indicates that a building once held the status and function of a cathedral but no longer does.
-
B.
cathedralSince
Indicates that an entity has held the status or function of a cathedral continuously from a specified point in time onward.
-
C.
coCathedral
Indicates that a church shares the status and functions of a cathedral with another cathedral within the same diocese or ecclesiastical jurisdiction.
-
D.
successorSeeCathedral
Indicates that a successor visits or observes a cathedral.
-
E.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: May 1, 2026, 1:52 a.m.