Triple
T9711493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of the Three Crosses, Imatra |
E235031
|
entity |
| Predicate | hasInteriorColorScheme |
P29272
|
FINISHED |
| Object | light, restrained palette |
—
|
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: light, restrained palette | Statement: [Church of the Three Crosses, Imatra, hasInteriorColorScheme, light, restrained palette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteriorColorScheme Context triple: [Church of the Three Crosses, Imatra, hasInteriorColorScheme, light, restrained palette]
-
A.
hasInteriorColor
Indicates that an entity possesses a specific color used on its interior surfaces or internal parts.
-
B.
hasColourScheme
chosen
Indicates that an entity is associated with a particular set or pattern of colors used in its design or appearance.
-
C.
hasBodyColor
Indicates that an entity possesses a particular body color as one of its attributes.
-
D.
hasRoofColor
Indicates that an entity possesses a roof whose color is the specified value.
-
E.
hasTypicalSeatColor
Indicates that an entity is characteristically associated with a particular color of seat.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e0591208190aa57cc9e2aebafb7 |
completed | April 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:19 p.m.