Triple
T17750125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | oscypek |
E443089
|
entity |
| Predicate | surfaceDecoration |
P39184
|
FINISHED |
| Object | carved geometric patterns |
—
|
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: carved geometric patterns | Statement: [oscypek, surfaceDecoration, carved geometric patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceDecoration Context triple: [oscypek, surfaceDecoration, carved geometric patterns]
-
A.
surfaceFeatureOf
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
-
B.
decorationShape
chosen
Indicates the geometric or visual form that a decorative element or ornament takes in relation to the object it adorns.
-
C.
decoration
Indicates that one entity serves as an ornament or embellishing element for another entity, enhancing its appearance or style.
-
D.
decorations
Indicates that one entity adds, provides, or serves as ornamental or decorative elements for another entity.
-
E.
surfaceDescription
Indicates that one entity provides a textual or qualitative description of the surface characteristics or appearance 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48418c0188190beb31809b40e4648 |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.