Triple
T25163123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown family of Chicago |
E626495
|
entity |
| Predicate | significantWealthSource |
P8003
|
FINISHED |
| Object | General Dynamics shareholding |
—
|
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: General Dynamics shareholding | Statement: [Crown family of Chicago, significantWealthSource, General Dynamics shareholding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantWealthSource Context triple: [Crown family of Chicago, significantWealthSource, General Dynamics shareholding]
-
A.
hasWealthSource
Indicates that an entity derives its wealth or financial resources from a specified source.
-
B.
wealthSource
chosen
Indicates the relationship by which an entity obtains or derives its wealth from a particular source.
-
C.
wealthSymbol
Indicates that one entity serves as a representation or sign of wealth for another entity.
-
D.
majorRevenueSource
Indicates that one entity serves as the primary or dominant source of revenue for another entity.
-
E.
usesWealthFor
Indicates that one entity directs or allocates its wealth or financial resources toward another entity or purpose.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6:31 a.m.