Triple
T20197462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drexel Burnham Lambert |
E493125
|
entity |
| Predicate | majorClientType |
P809
|
FINISHED |
| Object | corporate raiders |
—
|
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: corporate raiders | Statement: [Drexel Burnham Lambert, majorClientType, corporate raiders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorClientType Context triple: [Drexel Burnham Lambert, majorClientType, corporate raiders]
-
A.
majorCustomer
Indicates that one entity is a primary or high-value customer of another entity, typically contributing a significant portion of business or revenue.
-
B.
majorType
Indicates that one entity is classified as the primary or main type/category of another entity.
-
C.
majorUser
Indicates that one user holds a primary, leading, or most significant role or status relative to other users in a given context.
-
D.
customerType
chosen
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad99d50819090ddb7b546c65321 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.