Triple
T27791507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alticor |
E701092
|
entity |
| Predicate | productCategoriesViaSubsidiaries |
P181217
|
FINISHED |
| Object | health and wellness products |
—
|
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: health and wellness products | Statement: [Alticor, productCategoriesViaSubsidiaries, health and wellness products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productCategoriesViaSubsidiaries Context triple: [Alticor, productCategoriesViaSubsidiaries, health and wellness products]
-
A.
dataVendorCategory
Indicates the classification or type category assigned to a data vendor within a defined taxonomy or grouping.
-
B.
subsidiaryIndustry
Indicates that a subsidiary company operates within or is associated with a particular industry sector.
-
C.
catalogCategory
Indicates that an item or entity is assigned to, or belongs within, a specific catalog category.
-
D.
dataCategories
Indicates the types or classifications of data that are associated with or involved in a given entity or interaction.
-
E.
manufacturerSubsidiaryOf
Indicates that a manufacturer operates as a subsidiary company that is owned or controlled by another entity.
- F. None of above. chosen
Provenance (4 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: April 27, 2026, 5:28 p.m.