Triple
T18916275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Lewis |
E462731
|
entity |
| Predicate | hasInvestmentType |
P4851
|
FINISHED |
| Object | equities |
—
|
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: equities | Statement: [Joe Lewis, hasInvestmentType, equities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInvestmentType Context triple: [Joe Lewis, hasInvestmentType, equities]
-
A.
hasFinancialInstrumentType
Indicates that an entity is associated with, or classified by, a specific type or category of financial instrument.
-
B.
hasInvestmentTheme
Indicates that an investment, fund, or financial product is associated with a particular overarching theme or strategic focus (such as technology, sustainability, or healthcare).
-
C.
investmentType
chosen
Indicates the specific category or nature of an investment associated with an entity or transaction.
-
D.
inversionType
Indicates the specific kind or category of inversion relationship that holds between entities, such as one being the reverse, opposite, or role-swapped form of the other.
-
E.
hasWealthType
Indicates that an entity possesses or is associated with a particular category or type of wealth.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c627724881909cf63c67d64321e8 |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.