Triple
T10605165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redstone family |
E275852
|
entity |
| Predicate | familyBusinessModel |
P8006
|
FINISHED |
| Object | family-controlled holding company |
—
|
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: family-controlled holding company | Statement: [Redstone family, familyBusinessModel, family-controlled holding company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyBusinessModel Context triple: [Redstone family, familyBusinessModel, family-controlled holding company]
-
A.
relatedFamilyBusiness
chosen
Indicates that there is a connection between entities through ownership, management, or involvement in the same family-run business or businesses.
-
B.
familyType
Indicates the specific familial relationship or category that characterizes how the related entities are connected as family.
-
C.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
D.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
E.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4a5df88190b993196ca7849a88 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
Created at: April 8, 2026, 7:32 p.m.