Triple
T24299178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Factory Benelux |
E606044
|
entity |
| Predicate | usesArtworkBy |
P70602
|
FINISHED |
| Object | Factory-associated designers |
—
|
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: Factory-associated designers | Statement: [Factory Benelux, usesArtworkBy, Factory-associated designers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesArtworkBy Context triple: [Factory Benelux, usesArtworkBy, Factory-associated designers]
-
A.
artworkBy
Indicates that one entity is the creator or artist responsible for producing the other entity as an artwork.
-
B.
includesArtBy
chosen
Indicates that one entity contains, features, or presents artwork created by another entity.
-
C.
artUse
Indicates that one entity uses, applies, or employs another entity within an artistic or creative context.
-
D.
associatedWithWorkOfArt
Indicates a relationship in which an entity is connected or related to a specific work of art, such as through creation, contribution, ownership, or contextual association.
-
E.
hasArtworksFrom
Indicates that one entity possesses or includes artworks that originate from or are created by another entity.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f2915d8ac881908d71ba529e30f434 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 12:09 a.m.