Triple
T37178374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Cartagena |
E921120
|
entity |
| Predicate | hasCathedralStatusIn |
P9022
|
FINISHED |
| Object | Murcia |
—
|
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: Murcia | Statement: [Diocese of Cartagena, hasCathedralStatusIn, Murcia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCathedralStatusIn Context triple: [Diocese of Cartagena, hasCathedralStatusIn, Murcia]
-
A.
hasCathedralStatusAt
Indicates that an entity holds cathedral status at or during a specified time or temporal context.
-
B.
hasCathedralStatusSince
Indicates the point in time from which something has held the official status of a cathedral.
-
C.
hasCathedralStatusGrantedBy
Indicates that cathedral status has been formally conferred on something (typically a church or building) by a specified granting authority.
-
D.
hasCathedralBasilicaStatus
Indicates that an entity (typically a church) holds the official ecclesiastical designation of a cathedral basilica.
-
E.
hasCathedralCity
chosen
Indicates that a particular city is officially recognized as the cathedral city associated with a given ecclesiastical jurisdiction or region.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fff86e544c81908063f61b876c9d78 |
completed | May 10, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fff7e7cb688190977eeca41aad25b9 |
completed | May 10, 2026, 3:13 a.m. |
Created at: May 3, 2026, 4:15 p.m.