Triple
T25074325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Trieste |
E628004
|
entity |
| Predicate | hasPrimaryChurchBuildingType |
P45953
|
FINISHED |
| Object | cathedral church |
—
|
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: cathedral church | Statement: [Diocese of Trieste, hasPrimaryChurchBuildingType, cathedral church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryChurchBuildingType Context triple: [Diocese of Trieste, hasPrimaryChurchBuildingType, cathedral church]
-
A.
hasChurchType
chosen
Indicates that one entity (typically a church) is classified as being of a particular church type or category.
-
B.
religiousBuildingInstanceOf
Indicates that a specific religious building is an instance of a particular class or type of religious building.
-
C.
hasCathedralType
Indicates that an entity is associated with, classified by, or designated as having a specific type or category of cathedral.
-
D.
hasCathedralDenomination
Indicates the religious denomination with which a cathedral is affiliated or to which it belongs.
-
E.
hasClericalStructure
Indicates that an entity possesses an organized clerical or administrative hierarchy or framework.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 18, 2026, 6:20 a.m.