Triple
T20660219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kohlberg & Company |
E507739
|
entity |
| Predicate | roleInTransactions |
P66571
|
FINISHED |
| Object | financial sponsor |
—
|
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: financial sponsor | Statement: [Kohlberg & Company, roleInTransactions, financial sponsor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTransactions Context triple: [Kohlberg & Company, roleInTransactions, financial sponsor]
-
A.
roleInBankingHistory
Indicates that an entity has a specific function, contribution, or significance within the historical development of banking.
-
B.
roleInFinance
chosen
Indicates that an entity holds a specific function, responsibility, or position within a financial context, system, or transaction.
-
C.
roleInCollateral
Indicates that an entity participates in or is assigned a specific role within a collateral arrangement or structure.
-
D.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
E.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
- 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_69e6b2f16adc8190b2b9a69586fa7444 |
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.