Triple
T35537898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curvation |
E1026978
|
entity |
| Predicate | hasStyleAttribute |
P1609
|
FINISHED |
| Object | fashion-forward |
—
|
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: fashion-forward | Statement: [Curvation, hasStyleAttribute, fashion-forward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStyleAttribute Context triple: [Curvation, hasStyleAttribute, fashion-forward]
-
A.
hasStyle
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
B.
hasStyleName
Indicates that an entity is associated with a particular style through a specific style name.
-
C.
hasSystemStyle
Indicates that one entity is associated with, or characterized by, a particular system-defined style of another entity.
-
D.
hasStyleIndex
Indicates that an entity is associated with a particular style identified by a specific index or position.
-
E.
hasRuleStyle
Indicates that an entity is associated with a particular rule-based style or formatting specification.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fff4530f908190afe9387f732c2b7e |
completed | May 10, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fff3c01a64819091196875b0c88607 |
completed | May 10, 2026, 2:56 a.m. |
Created at: May 3, 2026, 4:04 p.m.