Triple
T1629588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacred Heart Cathedral |
E35225
|
entity |
| Predicate | hasTransept |
P30382
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sacred Heart Cathedral, hasTransept, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransept Context triple: [Sacred Heart Cathedral, hasTransept, yes]
-
A.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
B.
hasMezzanine
Indicates that one entity includes or is equipped with a mezzanine level in relation to another entity.
-
C.
cathedral
Indicates that an entity is a cathedral, i.e., it has the status or function of a principal church, typically one that is the seat of a bishop.
-
D.
hasColonnade
Indicates that one entity features or is characterized by a colonnade in relation to another entity.
-
E.
isDomedChurch
Indicates that a church building features one or more domes as a defining architectural element.
- F. None of above. chosen
Provenance (4 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9431af5ac8190893133f1ae490142 |
completed | March 5, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69a907c91c888190b6ed295c1a2e0977 |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a94319becc819089c2daf45fe08a0c |
completed | March 5, 2026, 8:47 a.m. |
Created at: March 4, 2026, 7:28 p.m.