Triple
T28699548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GS Capital Partners |
E729510
|
entity |
| Predicate | hasFundSeries |
P17331
|
FINISHED |
| Object | GS Capital Partners I |
—
|
NE NERFINISHED |
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: GS Capital Partners I | Statement: [GS Capital Partners, hasFundSeries, GS Capital Partners I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFundSeries Context triple: [GS Capital Partners, hasFundSeries, GS Capital Partners I]
-
A.
hasSubFund
chosen
Indicates that an entity (typically a fund) includes or controls another fund as a subordinate or component fund within its structure.
-
B.
hasStockSeries
Indicates that an entity is associated with a particular stock time series or sequence of stock-related data.
-
C.
hasSupportSeries
Indicates that one entity is backed, reinforced, or maintained by a sequence or set of supporting elements provided by another entity.
-
D.
hasSubSeries
Indicates that one series is a subordinate or component series within a larger parent series.
-
E.
hasStandardSeries
Indicates that an entity is associated with, or belongs to, a designated standard series or standardized sequence.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 5:41 a.m.