Triple
T21048103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Y-blokka |
E518500
|
entity |
| Predicate | hasArtIntegrationTechnique |
P3047
|
FINISHED |
| Object | concrete sandblasting |
—
|
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: concrete sandblasting | Statement: [Y-blokka, hasArtIntegrationTechnique, concrete sandblasting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtIntegrationTechnique Context triple: [Y-blokka, hasArtIntegrationTechnique, concrete sandblasting]
-
A.
hasArtFeature
Indicates that an entity possesses or is characterized by a particular artistic attribute, element, or stylistic feature.
-
B.
hasTechnique
chosen
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
C.
artisticTechnique
Indicates the method, style, or process used to create or execute an artistic work.
-
D.
hasTechnicalElement
Indicates that something includes, involves, or is characterized by a technical component, feature, or aspect.
-
E.
hasArtisticStrategy
Indicates that an entity employs or is associated with a particular artistic approach, method, or plan in creating or presenting art.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf5b01481909db49aa5be3846aa |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:34 p.m.