Triple
T21866329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baguette bag |
E539891
|
entity |
| Predicate | hasReissues |
P136885
|
FINISHED |
| Object | multiple re-editions over the years |
—
|
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: multiple re-editions over the years | Statement: [Baguette bag, hasReissues, multiple re-editions over the years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReissues Context triple: [Baguette bag, hasReissues, multiple re-editions over the years]
-
A.
wasReissued
Indicates that an item, such as a document or edition, has been issued again after its original release.
-
B.
hasSubsequentReissue
Indicates that one entity is a later reissued version that follows another entity in sequence.
-
C.
hasReissueHistory
chosen
Indicates that an entity has a record of being reissued or having undergone one or more reissue events in its history.
-
D.
reissueIncludes
Indicates that a reissued version of something contains or incorporates the referenced item as part of that reissue.
-
E.
hasReissueProgram
Indicates that an entity offers a program or process for issuing replacements or updated versions of something previously provided.
- 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.