Triple
T9711673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artek |
E235035
|
entity |
| Predicate | hasDesignHeritageFrom |
P18613
|
FINISHED |
| Object | Finnish modernism |
—
|
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: Finnish modernism | Statement: [Artek, hasDesignHeritageFrom, Finnish modernism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignHeritageFrom Context triple: [Artek, hasDesignHeritageFrom, Finnish modernism]
-
A.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
B.
designHeritage
chosen
Indicates that one entity has influenced, shaped, or contributed to the design tradition or stylistic lineage of another entity.
-
C.
hasHeritageValueFor
Indicates that something possesses cultural, historical, or heritage significance for a particular entity or community.
-
D.
hasDesignOrigin
Indicates that one entity is the source, inspiration, or original model from which the design of another entity is derived.
-
E.
hasHeritageFeature
Indicates that an entity possesses or includes a feature recognized as part of cultural, historical, or natural heritage.
- 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.