Triple
T35810170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Styles Clash |
E1035206
|
entity |
| Predicate | inspiredVariant |
P193218
|
FINISHED |
| Object | Belly‑to‑back Styles Clash |
—
|
NE NERFINISHED |
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: Belly‑to‑back Styles Clash | Statement: [Styles Clash, inspiredVariant, Belly‑to‑back Styles Clash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredVariant Context triple: [Styles Clash, inspiredVariant, Belly‑to‑back Styles Clash]
-
A.
inspiredVariations
chosen
Indicates that one entity consists of versions, adaptations, or reinterpretations that were creatively influenced by another entity.
-
B.
customizedVariantOf
Indicates that one entity is a modified or tailored version derived from another, preserving a core basis while introducing specific customizations.
-
C.
designVariant
Indicates that one entity is an alternative design or version derived from or related to another entity’s design.
-
D.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
E.
inspiredOtherPattern
Indicates that one pattern served as a source of inspiration or influence for the development or design of another pattern.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 3, 2026, 4:06 p.m.