Triple
T30776027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symington |
E783671
|
entity |
| Predicate | parishChurchArchitecturalStyle |
P75549
|
FINISHED |
| Object | Romanesque |
—
|
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: Romanesque | Statement: [Symington, parishChurchArchitecturalStyle, Romanesque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishChurchArchitecturalStyle Context triple: [Symington, parishChurchArchitecturalStyle, Romanesque]
-
A.
parishChurchArchitectureStyle
chosen
Indicates the architectural style or design tradition in which a parish church is built or characterized.
-
B.
hasParishChurchArchitecturalInterest
Indicates that a parish church possesses notable architectural features or significance.
-
C.
isParishChurch
Indicates that a church holds the official status of the main church serving a particular parish within an ecclesiastical jurisdiction.
-
D.
parishChurchCentury
Indicates the century during which a given parish church was established, built, or primarily dates from.
-
E.
parishChurchFeatures
Indicates that a parish church possesses or includes specific architectural, artistic, or functional features.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fe119788190afd49e20e189f3ef |
completed | May 2, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:40 p.m.