Triple
T28682261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KMB |
E726037
|
entity |
| Predicate | tickerForIndustry |
P24922
|
FINISHED |
| Object | Consumer 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: Consumer products | Statement: [KMB, tickerForIndustry, Consumer products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tickerForIndustry Context triple: [KMB, tickerForIndustry, Consumer products]
-
A.
tickerFor
Indicates that one entity is the stock ticker symbol used to uniquely identify another entity (typically a publicly traded company or security) in financial markets.
-
B.
industryExposure
Indicates the extent to which an entity is involved in, affected by, or financially linked to a particular industry or set of industries.
-
C.
industryStatus
Indicates the current operational or regulatory condition of an entity within its industry (e.g., active, inactive, regulated, or restricted status).
-
D.
industryContext
chosen
Indicates the industry or sector within which an entity, activity, or relationship is situated or most relevant.
-
E.
sectorInfluence
Indicates the degree to which one sector affects, shapes, or exerts control over another sector or over outcomes within that sector.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 5:10 a.m.