Triple
T27065074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Andrew’s Church, Corby Glen |
E685150
|
entity |
| Predicate | hasWallPaintingsStyle |
P108769
|
FINISHED |
| Object | medieval figurative painting |
—
|
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: medieval figurative painting | Statement: [St Andrew’s Church, Corby Glen, hasWallPaintingsStyle, medieval figurative painting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWallPaintingsStyle Context triple: [St Andrew’s Church, Corby Glen, hasWallPaintingsStyle, medieval figurative painting]
-
A.
hasWallPaintingStyle
chosen
Indicates that an entity features or is associated with a particular style or type of wall painting.
-
B.
hasWallPaintingsOn
Indicates that wall paintings are present on or applied to a specified surface or structure.
-
C.
hasMuralsDepicting
Indicates that one entity contains or features murals that visually represent or portray another entity.
-
D.
hasWorkPaintedOnWalls
Indicates that an entity has created or produced artwork that is painted on walls.
-
E.
hasMuralsFrom
Indicates that a location or structure contains murals that originate from or were created in a specified place or time period.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 8:24 a.m.