Triple
T17254221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starwood Capital Group |
E418836
|
entity |
| Predicate | raisesCapitalThrough |
P51929
|
FINISHED |
| Object | private funds |
—
|
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: private funds | Statement: [Starwood Capital Group, raisesCapitalThrough, private funds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raisesCapitalThrough Context triple: [Starwood Capital Group, raisesCapitalThrough, private funds]
-
A.
raisesCapitalFrom
chosen
Indicates that one entity obtains funding or financial resources from another entity.
-
B.
possibleCapital
Indicates that a location is a candidate or potential capital city of a given political or administrative entity.
-
C.
capitalizedOn
Indicates that one entity took advantage of, exploited, or made beneficial use of an opportunity, situation, or resource provided or created by another entity.
-
D.
recognizesCapital
Indicates that one entity acknowledges or identifies another entity as the capital of a given region or country.
-
E.
hasLaterCapital
Indicates that one entity’s designation or establishment as a capital city occurred later in time than that of 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e6b2b1c8190b446ce648ecaad80 |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.