Triple
T9307505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of St. Mary and the Martyrs |
E223923
|
entity |
| Predicate | domeSpan |
P28935
|
FINISHED |
| Object | approximately equal to its interior height |
—
|
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: approximately equal to its interior height | Statement: [Church of St. Mary and the Martyrs, domeSpan, approximately equal to its interior height]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domeSpan Context triple: [Church of St. Mary and the Martyrs, domeSpan, approximately equal to its interior height]
-
A.
diameterOfDome
chosen
Indicates the measurement of the dome’s diameter as a geometric property of that dome.
-
B.
heightOfDome
Indicates the measured vertical extent or elevation of a dome structure from its base to its highest point.
-
C.
domeWeight
Indicates the weight or mass of a dome structure associated with an entity.
-
D.
domeShape
Indicates that one entity has a dome-like or hemispherical shape in relation to another or in its overall form.
-
E.
hasDomeOrSpire
Indicates that one entity possesses or features a dome or spire as part of its 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd1daa21188190b1b2e508b0d09dcb |
completed | April 1, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.