Triple
T13149787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vologda lace |
E312432
|
entity |
| Predicate | patternMotif |
P41002
|
FINISHED |
| Object | flowers |
—
|
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: flowers | Statement: [Vologda lace, patternMotif, flowers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patternMotif Context triple: [Vologda lace, patternMotif, flowers]
-
A.
pattern
Indicates that one entity exhibits, follows, or is characterized by a particular recurring form, structure, or arrangement associated with another entity.
-
B.
featuresMotif
chosen
Indicates that something contains, incorporates, or prominently includes a particular recurring motif or pattern.
-
C.
patroonOf
Indicates a relationship in which one entity acts as a patron, sponsor, or protector providing support or resources to another entity.
-
D.
maskPattern
Indicates a relationship where one entity serves as a masking template or pattern that determines which parts or aspects of another entity are revealed, hidden, or transformed.
-
E.
kitPattern
Indicates the design or visual pattern featured on a team's kit or uniform.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:11 p.m.