Triple
T16000978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chesebrough Manufacturing Company |
E388089
|
entity |
| Predicate | developedProcessFor |
P73
|
FINISHED |
| Object | refining petroleum jelly for consumer use |
—
|
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: refining petroleum jelly for consumer use | Statement: [Chesebrough Manufacturing Company, developedProcessFor, refining petroleum jelly for consumer use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedProcessFor Context triple: [Chesebrough Manufacturing Company, developedProcessFor, refining petroleum jelly for consumer use]
-
A.
developmentProcessIncludes
Indicates that a particular activity, phase, or component is part of, or contained within, a broader development process.
-
B.
developedThrough
Indicates that something came into existence, was created, or was brought to its current form by means of a specified process, method, or developmental pathway.
-
C.
developed
chosen
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
-
D.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
-
E.
documentedProcess
Indicates that a process has been formally recorded, described, or specified in documentation.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142dc081c819082527e3fa8773460 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:55 a.m.