Triple
T35920487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mola blouses |
E1038867
|
entity |
| Predicate | hasPatternLayout |
P8151
|
FINISHED |
| Object | symmetrical design |
—
|
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: symmetrical design | Statement: [mola blouses, hasPatternLayout, symmetrical design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatternLayout Context triple: [mola blouses, hasPatternLayout, symmetrical design]
-
A.
hasPattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
B.
hasPatternPlacement
Indicates the spatial or positional arrangement of a pattern relative to or on another entity.
-
C.
hasStandardLayout
Indicates that an entity follows a predefined or commonly accepted arrangement or structure.
-
D.
hasUsePattern
Indicates a characteristic or recurring way in which something is typically used or applied.
-
E.
hasScalePattern
Indicates that an entity possesses a specific arrangement or pattern in its scales.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffebbd9bac8190b3dca4b7252a2278 |
completed | May 10, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69ffe93120a08190a44bb64d052eda78 |
completed | May 10, 2026, 2:10 a.m. |
Created at: May 3, 2026, 4:07 p.m.