Triple
T29259747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heritage Brands |
E741806
|
entity |
| Predicate | portfolioRationale |
P6735
|
FINISHED |
| Object | monetize legacy labels |
—
|
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: monetize legacy labels | Statement: [Heritage Brands, portfolioRationale, monetize legacy labels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portfolioRationale Context triple: [Heritage Brands, portfolioRationale, monetize legacy labels]
-
A.
portfolioWithin
Indicates that one portfolio is contained within, or is a subset of, another portfolio.
-
B.
economicRationale
chosen
Indicates the underlying economic reasoning or justification that explains why a particular decision, action, or relationship is expected to be financially or resource-efficient.
-
C.
portfolioAssignmentBy
Indicates that a portfolio is assigned or allocated by a particular agent or entity.
-
D.
vestmentStyle
Indicates the style or type of clothing or ceremonial garments associated with an entity.
-
E.
investorObjective
Indicates that an entity’s goal, preference, or intended outcome in its role as an investor is directed toward another entity or investment.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f664b1145881908aed111df0493cab |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:40 p.m.