Triple
T31990890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolmen ristin kirkko |
E816864
|
entity |
| Predicate | hasWindowDesign |
P1529
|
FINISHED |
| Object | three-cross motif windows |
—
|
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: three-cross motif windows | Statement: [Kolmen ristin kirkko, hasWindowDesign, three-cross motif windows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWindowDesign Context triple: [Kolmen ristin kirkko, hasWindowDesign, three-cross motif windows]
-
A.
hasWindowDesigner
Indicates that an entity has another entity serving as the designer or creator of its window(s).
-
B.
hasDesign
chosen
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
C.
hasGlassCurtainWall
Indicates that a building or structure features an exterior façade primarily composed of a non-load-bearing glass curtain wall system.
-
D.
windowMaterial
Indicates the material from which a window is made or constructed.
-
E.
hasDomeDesign
Indicates that one entity features or incorporates the dome design of another entity.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 12:13 a.m.