Triple
T18906096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forstmann Little & Co. |
E462465
|
entity |
| Predicate | notableExit |
P79929
|
FINISHED |
| Object | sale of Gulfstream Aerospace to General Dynamics |
—
|
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 of Gulfstream Aerospace to General Dynamics | Statement: [Forstmann Little & Co., notableExit, sale of Gulfstream Aerospace to General Dynamics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableExit Context triple: [Forstmann Little & Co., notableExit, sale of Gulfstream Aerospace to General Dynamics]
-
A.
notableDeparture
chosen
Indicates that an entity has left a position, place, or role in a way that is significant or noteworthy.
-
B.
notableEnding
Indicates that an entity concludes or finishes in a way that is remarkable, memorable, or otherwise noteworthy.
-
C.
notableGate
Indicates that a gate is recognized as significant, prominent, or noteworthy in some context.
-
D.
notablePass
Indicates that one entity is recognized for having successfully passed or cleared another entity, such as a test, threshold, or evaluation, in a notably significant way.
-
E.
notableCrossing
Indicates that one entity is a significant or well-known crossing point (such as a bridge, pass, or intersection) associated with another entity.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c52cc9cc8190ac489d36e51693c8 |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.