Triple
T20660228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kohlberg & Company |
E507739
|
entity |
| Predicate | exitRoutes |
P140954
|
FINISHED |
| Object | sale to strategic buyers |
—
|
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: sale to strategic buyers | Statement: [Kohlberg & Company, exitRoutes, sale to strategic buyers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exitRoutes Context triple: [Kohlberg & Company, exitRoutes, sale to strategic buyers]
-
A.
exitTo
Indicates that one location or entity serves as a passage or route leading directly to another location or entity.
-
B.
usedRoutes
Indicates that an entity has utilized or traveled along specific routes.
-
C.
routesFrom
Indicates that something (such as a path, connection, or communication) originates at one entity and is directed or carried from that source entity toward another.
-
D.
exitsThrough
Indicates that an entity leaves or departs from a place, structure, or area by passing through a specified exit or passage.
-
E.
avoidsRoute
Indicates that an entity deliberately does not use or travel along a particular route.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:44 a.m.