Triple
T23448528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RMS |
E565609
|
entity |
| Predicate | associatedCompanyKnownFor |
P152330
|
FINISHED |
| Object | high-end fashion |
—
|
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: high-end fashion | Statement: [RMS, associatedCompanyKnownFor, high-end fashion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCompanyKnownFor Context triple: [RMS, associatedCompanyKnownFor, high-end fashion]
-
A.
associatedCompanyNotableRole
Indicates that an entity has a notable role or position in a specified associated company.
-
B.
associatedCompanyGlobalScope
Indicates that there is a relationship linking an entity to a company at a global (worldwide) organizational scope.
-
C.
relatedCompanyType
Indicates the type or nature of the relationship that one company has to another company.
-
D.
associatedCompanyFate
Indicates that there is a relationship between an entity and the outcome or final status (e.g., closure, acquisition, bankruptcy) of a company with which it is or was associated.
-
E.
associatedCompanyMainProductLine
Indicates that a company’s primary or main line of products is linked or related to a specified product category or product line.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a64b27988190b4722425da964407 |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:52 p.m.