Triple
T7249776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dalmeny, Scotland |
E156566
|
entity |
| Predicate | parishChurchArchitectureStyle |
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: [Dalmeny, Scotland, parishChurchArchitectureStyle, Romanesque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishChurchArchitectureStyle Context triple: [Dalmeny, Scotland, parishChurchArchitectureStyle, Romanesque]
-
A.
parishChurchFeatures
Indicates that a parish church possesses or includes specific architectural, artistic, or functional features.
-
B.
ecclesiasticalStyle
Indicates the formal religious or clerical style or title by which an ecclesiastical person is properly addressed.
-
C.
parishChurchDenomination
Indicates the religious denomination with which a parish church is formally affiliated.
-
D.
parishChurchName
Indicates the name of the parish church associated with a given entity.
-
E.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
- 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_69c68827b5e481908dc05e145b2c92d4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea77a3588190accf31860170f052 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e889854481908c765ce2107f2d3a |
completed | March 27, 2026, 8:28 p.m. |
Created at: March 27, 2026, 2:56 p.m.