Triple
T22167270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingswood Capital Management |
E547826
|
entity |
| Predicate | hasRevenueModel |
P94216
|
FINISHED |
| Object | management fees |
—
|
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: management fees | Statement: [Kingswood Capital Management, hasRevenueModel, management fees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevenueModel Context triple: [Kingswood Capital Management, hasRevenueModel, management fees]
-
A.
usesRevenueModel
chosen
Indicates that one entity applies or operates according to a particular revenue model to generate income.
-
B.
hasRevenueSystem
Indicates that one entity possesses, uses, or is associated with a particular revenue-generating system or mechanism.
-
C.
hasRevenueUnit
Indicates that an entity’s revenue is measured, reported, or associated in terms of a specified unit (e.g., currency or measurement unit).
-
D.
hasBroadcastRevenueModel
Indicates that one entity uses or is associated with a particular revenue model based on broadcasting activities.
-
E.
hasBusinessModelCharacteristic
Indicates that a business model possesses or exhibits a specific feature, quality, or attribute.
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a3213ec8190841439dbe470d545 |
completed | April 28, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.