Triple
T19274648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mimico Presbyterian Church |
E482015
|
entity |
| Predicate | hasArchitectureUse |
P22013
|
FINISHED |
| Object | ecclesiastical building |
—
|
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: ecclesiastical building | Statement: [Mimico Presbyterian Church, hasArchitectureUse, ecclesiastical building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchitectureUse Context triple: [Mimico Presbyterian Church, hasArchitectureUse, ecclesiastical building]
-
A.
hasArchitectureBy
Indicates that an entity’s architectural design was created or authored by a specified architect or architectural firm.
-
B.
usesArchitecture
Indicates that one entity is built, implemented, or operates according to the architectural style, framework, or design specified by another entity.
-
C.
usesArchitectureComponent
Indicates that one entity employs or incorporates a specific architecture component as part of its structure, design, or implementation.
-
D.
architectureCanUse
Indicates that a particular architecture is capable of employing, incorporating, or being built with a specified component, technique, or resource.
-
E.
architecturalUse
chosen
Indicates how a structure, space, or element is intended to be used or function within an architectural context.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbbb2fc08190b417a6d0b7a9d6b8 |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.