Triple
T29037839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raymond James Financial, Inc. |
E737912
|
entity |
| Predicate | clientSegments |
P82393
|
FINISHED |
| Object | individual investors |
—
|
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: individual investors | Statement: [Raymond James Financial, Inc., clientSegments, individual investors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientSegments Context triple: [Raymond James Financial, Inc., clientSegments, individual investors]
-
A.
customerGroup
chosen
Indicates a relationship in which an entity belongs to, is classified under, or is associated with a particular group of customers.
-
B.
passengerSegments
Indicates a relationship where a journey or trip is divided into distinct legs or segments that a passenger travels through.
-
C.
marketSegmentType
Indicates the specific category or segment of the market that an entity, product, or service is targeted toward or associated with.
-
D.
hasUserSegment
Indicates that an entity is associated with a particular user segment or group of users defined by shared characteristics or behaviors.
-
E.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6603e70308190a25e074c705d1cb0 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:59 a.m.