Triple
T26310315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YSL |
E661802
|
entity |
| Predicate | creativeDirectorStartDate |
P116026
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [YSL, creativeDirectorStartDate, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creativeDirectorStartDate Context triple: [YSL, creativeDirectorStartDate, 2016]
-
A.
hasCreativeDirectorRoleAt
Indicates that an entity holds the position or responsibilities of a creative director at a specified organization or project.
-
B.
artisticDirectorStart
Indicates the date or point in time when someone begins serving in the role of artistic director for an organization or production.
-
C.
creativeDirectorStartYearAtGivenchy
chosen
Indicates the year in which an individual began serving as creative director at Givenchy.
-
D.
creatorLifespan
Indicates the time period between the birth and death of the creator associated with an entity.
-
E.
partnerStartDate
Indicates the date on which the partnership or partner relationship between the entities begins.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 26, 2026, 10:21 p.m.