Triple
T38156527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dior haute couture collections |
E952900
|
entity |
| Predicate | clientService |
P190153
|
FINISHED |
| Object | made-to-measure fittings |
—
|
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: made-to-measure fittings | Statement: [Dior haute couture collections, clientService, made-to-measure fittings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientService Context triple: [Dior haute couture collections, clientService, made-to-measure fittings]
-
A.
clientServiceModel
Indicates a relationship where a particular service model is provided, managed, or applied for a given client.
-
B.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
C.
clientFor
Indicates that one entity acts as a client that uses the services, resources, or interface provided by another entity.
-
D.
serviceUser
Indicates that one entity is a user or consumer of a service provided by another entity.
-
E.
launchServiceCustomer
Indicates that a customer is the recipient or user of a launch service provided by another entity.
- F. None of above. chosen
Provenance (4 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcb088aac481909db90804faff315f |
completed | May 7, 2026, 3:32 p.m. |
Created at: May 3, 2026, 4:21 p.m.