Triple
T22111675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senneh knot |
E546431
|
entity |
| Predicate | patternAssociation |
P8034
|
FINISHED |
| Object | curvilinear Persian designs |
—
|
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: curvilinear Persian designs | Statement: [Senneh knot, patternAssociation, curvilinear Persian designs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patternAssociation Context triple: [Senneh knot, patternAssociation, curvilinear Persian designs]
-
A.
pattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a particular recurring form, structure, or arrangement associated with another entity.
-
B.
patternRelationship
Indicates a relationship where one entity serves as a pattern, template, or recurring configuration that another entity follows, matches, or is derived from.
-
C.
patternShownTo
Indicates that a particular pattern is presented or displayed to an entity (such as a user or system) for viewing or use.
-
D.
shapeAssociation
Indicates a relationship where one entity is associated with, characterized by, or linked to a particular shape of another entity.
-
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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12949cc7881908898ca7dc130f57f |
completed | April 28, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.