Triple
T30076333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inverted Collar and Tie |
E764329
|
entity |
| Predicate | creatorRoleOfCoosjeVanBruggen |
P13180
|
FINISHED |
| Object | conceptual design |
—
|
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: conceptual design | Statement: [Inverted Collar and Tie, creatorRoleOfCoosjeVanBruggen, conceptual design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creatorRoleOfCoosjeVanBruggen Context triple: [Inverted Collar and Tie, creatorRoleOfCoosjeVanBruggen, conceptual design]
-
A.
créateur
Indicates that an entity is the creator or originator of another entity.
-
B.
creatorAlternativeName
Indicates an alternative or variant name used to refer to the creator.
-
C.
composerOfDepictingWork
Indicates that an entity is the composer of a musical work that is itself a depiction or representation of another entity or subject.
-
D.
creatorRoleOfComposer
Indicates that an entity serves in the role of composer as the creator of another entity.
-
E.
creatorType
chosen
Indicates the role or category of a creator in relation to the creation of something (e.g., author, artist, director).
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 29, 2026, 7:02 p.m.