Triple
T21866311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baguette bag |
E539891
|
entity |
| Predicate | becameFashionPhenomenonInPeriod |
P105129
|
FINISHED |
| Object | late 1990s |
—
|
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: late 1990s | Statement: [Baguette bag, becameFashionPhenomenonInPeriod, late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameFashionPhenomenonInPeriod Context triple: [Baguette bag, becameFashionPhenomenonInPeriod, late 1990s]
-
A.
wasFashionableIn
Indicates that something was considered stylish, popular, or in vogue during a particular time period or era.
-
B.
stylePeriod
Indicates the stylistic or historical period with which an entity (such as an artwork, artifact, or performance) is associated.
-
C.
gainedProminenceAs
Indicates that an entity became widely recognized or notable in the role, capacity, or identity specified by another entity.
-
D.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
E.
notablePopularityPeriod
chosen
Indicates the time span during which something was especially popular or widely recognized.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d63f2ec48190956a3e99d8f98b1f |
completed | April 28, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.