Triple
T20660193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kohlberg & Company |
E507739
|
entity |
| Predicate | typicalTransactionType |
P72355
|
FINISHED |
| Object | leveraged buyout |
—
|
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: leveraged buyout | Statement: [Kohlberg & Company, typicalTransactionType, leveraged buyout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTransactionType Context triple: [Kohlberg & Company, typicalTransactionType, leveraged buyout]
-
A.
associatedWithTransactionType
chosen
Indicates that something has a connection or linkage to a specific type or category of transaction.
-
B.
transactionNature
Indicates the type or character of a transaction, specifying what kind of exchange or operation is taking place between the involved parties.
-
C.
typicalTargetType
Indicates the usual or most common type or category of entity that serves as the target or recipient in a given relationship or action.
-
D.
typicalEntryType
Indicates the usual or standard category or kind of entry associated with something.
-
E.
transactionField
Indicates that a specific data field is associated with, or belongs to, a particular transaction.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2eff7a88190be0bdea227616e02 |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.