Triple
T34596401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W. R. Grace and Company |
E888320
|
entity |
| Predicate | customerIndustry |
P71415
|
FINISHED |
| Object | petrochemical industry |
—
|
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: petrochemical industry | Statement: [W. R. Grace and Company, customerIndustry, petrochemical industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customerIndustry Context triple: [W. R. Grace and Company, customerIndustry, petrochemical industry]
-
A.
hasCustomerIndustry
chosen
Indicates that a customer is associated with or operates within a particular industry or sector.
-
B.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
C.
industryStart
Indicates the point in time or event at which an industry, industrial activity, or industrial era begins.
-
D.
industryExposure
Indicates the extent to which an entity is involved in, affected by, or financially linked to a particular industry or set of industries.
-
E.
industryContext
Indicates the industry or sector within which an entity, activity, or relationship is situated or most relevant.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:03 a.m.