Triple
T34087460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander McQueen Spring/Summer 2010 |
E874210
|
entity |
| Predicate | footwearDesigner |
P184
|
FINISHED |
| Object | Alexander McQueen |
—
|
NE NERFINISHED |
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: Alexander McQueen | Statement: [Alexander McQueen Spring/Summer 2010, footwearDesigner, Alexander McQueen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footwearDesigner Context triple: [Alexander McQueen Spring/Summer 2010, footwearDesigner, Alexander McQueen]
-
A.
shoeEndorsement
Indicates a relationship where an entity publicly supports or promotes a particular shoe or shoe brand, typically as part of a sponsorship or marketing agreement.
-
B.
shoeLine
Indicates a relationship where a shoe is part of, or belongs to, a particular product line or collection of shoes.
-
C.
footwearCategory
Indicates the classification of an item based on the type or category of footwear it belongs to.
-
D.
designedBy
chosen
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
E.
designerAlias
Indicates that one name or label is used as an alternative alias for a designer.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c0c98348190a776048337eaf376 |
completed | May 3, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:52 a.m.