Triple
T18190367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MS |
E435515
|
entity |
| Predicate | associatedCompanyClientTypes |
P97362
|
FINISHED |
| Object | institutional clients |
—
|
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: institutional clients | Statement: [MS, associatedCompanyClientTypes, institutional clients]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCompanyClientTypes Context triple: [MS, associatedCompanyClientTypes, institutional clients]
-
A.
relatedCompanyType
Indicates the type or nature of the relationship that one company has to another company.
-
B.
belongsToCompanyType
Indicates that an entity is associated with or classified under a particular type or category of company.
-
C.
underlyingCompanyCustomerType
chosen
Indicates the type or category of customer relationship that an underlying company has (e.g., retail, institutional, corporate).
-
D.
hasAssociatedCompany
Indicates that one entity is linked or connected to a company in an associated or affiliated manner.
-
E.
associatedCompanyBusinessSegment
Indicates that a company is linked to a specific business segment through its operations, products, or services.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0016ec08190ae853dbc89865a41 |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.