Triple
T26533027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | poor boy sweater |
E670870
|
entity |
| Predicate | fashionEra |
P18647
|
FINISHED |
| Object | 1960s fashion |
—
|
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: 1960s fashion | Statement: [poor boy sweater, fashionEra, 1960s fashion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fashionEra Context triple: [poor boy sweater, fashionEra, 1960s fashion]
-
A.
fashionStyle
Indicates the characteristic way in which an entity dresses or presents themselves in terms of clothing and appearance.
-
B.
stylePeriod
chosen
Indicates the stylistic or historical period with which an entity (such as an artwork, artifact, or performance) is associated.
-
C.
visualEra
Indicates the historical or stylistic period to which the visual appearance or design of something belongs.
-
D.
curatesEra
Indicates a relationship where an entity organizes, selects, or manages items, information, or works specifically associated with a particular historical or thematic era.
-
E.
fashionCategory
Indicates the classification of an item into a specific fashion-related category or type (e.g., clothing, footwear, accessories).
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 1:36 a.m.