Triple
T34409627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denver parish |
E883217
|
entity |
| Predicate | historicChurchBuilding |
P38129
|
FINISHED |
| Object | St Mary’s Church, Denver |
—
|
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: St Mary’s Church, Denver | Statement: [Denver parish, historicChurchBuilding, St Mary’s Church, Denver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicChurchBuilding Context triple: [Denver parish, historicChurchBuilding, St Mary’s Church, Denver]
-
A.
isHistoricChurchIn
Indicates that a church, recognized as historic, is located within a specified geographic area or jurisdiction.
-
B.
hasHistoricChurches
chosen
Indicates that an entity possesses or contains one or more churches of recognized historical significance.
-
C.
historicDenomination
Indicates that an entity was formerly associated with a particular religious denomination or branch in the past, even if that affiliation has since changed.
-
D.
formerReligiousBuilding
Indicates that a building previously served a religious function but no longer does so.
-
E.
historicStructureArchitect
Indicates that an architect is the designer or primary planner responsible for a particular historic structure.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a006417d1f4819093b2da02dbf2ab22 |
completed | May 10, 2026, 10:55 a.m. |
| PD | Predicate disambiguation | batch_6a00634a7a748190ac4774493fce3d30 |
completed | May 10, 2026, 10:51 a.m. |
Created at: May 1, 2026, 1:59 a.m.