Triple
T20660216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kohlberg & Company |
E507739
|
entity |
| Predicate | capitalStructureTools |
P13431
|
FINISHED |
| Object | leverage |
—
|
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: leverage | Statement: [Kohlberg & Company, capitalStructureTools, leverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalStructureTools Context triple: [Kohlberg & Company, capitalStructureTools, leverage]
-
A.
capitalStructure
chosen
Indicates the financial relationship defining how an entity is funded through a mix of debt, equity, and other securities.
-
B.
sharesOutstanding
Indicates the total number of a company’s shares that are currently issued and held by all shareholders, excluding any shares the company has repurchased.
-
C.
authorizedCapital
Indicates the legally approved maximum amount of share capital that a company is permitted to issue under its corporate charter or governing documents.
-
D.
sharesCapitalBetween
Indicates a relationship where the ownership capital or equity is distributed or jointly held between two or more entities.
-
E.
capitalDividedInto
Indicates that the capital city is partitioned into distinct administrative or geographic subdivisions.
- 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.