Triple
T29399588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elie Saab |
E745597
|
entity |
| Predicate | clientsInclude |
P151560
|
FINISHED |
| Object | Hollywood actresses |
—
|
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: Hollywood actresses | Statement: [Elie Saab, clientsInclude, Hollywood actresses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientsInclude Context triple: [Elie Saab, clientsInclude, Hollywood actresses]
-
A.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
B.
includedMembersOf
chosen
Indicates that certain members or elements are contained within, or form part of, a specified group or collection.
-
C.
managementIncludes
Indicates that a management entity encompasses, oversees, or has responsibility for the included entity or entities.
-
D.
hasCustomers
Indicates that an entity maintains a business relationship in which other entities purchase or receive its goods or services as customers.
-
E.
clientServiceModel
Indicates a relationship where a particular service model is provided, managed, or applied for a given client.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a06aa2c8190aa13c6561f6838b7 |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 2:49 p.m.