Triple
T14815027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalostotitlán |
E348288
|
entity |
| Predicate | hasCatholicChurch |
P15000
|
FINISHED |
| Object | parish churches in the historic center |
—
|
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: parish churches in the historic center | Statement: [Jalostotitlán, hasCatholicChurch, parish churches in the historic center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatholicChurch Context triple: [Jalostotitlán, hasCatholicChurch, parish churches in the historic center]
-
A.
hasCatholicCathedral
Indicates that a place or jurisdiction possesses at least one officially recognized Catholic cathedral within its boundaries.
-
B.
hasCathedralDenomination
Indicates the religious denomination with which a cathedral is affiliated or to which it belongs.
-
C.
hasCatholicDiocese
Indicates that a specified place or region falls under the jurisdiction of a particular Catholic diocese.
-
D.
hasChurch
chosen
Indicates that a place or entity possesses, contains, or is associated with a church.
-
E.
hasCathedralParish
Indicates that a cathedral is associated with or served by a specific parish within an ecclesiastical jurisdiction.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe0e89c81908c0e1fe2bc3ebcfc |
completed | April 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:49 a.m.