Triple
T35886597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marlex polyethylene |
E1037660
|
entity |
| Predicate | hasPolymerType |
P81139
|
FINISHED |
| Object | polyethylene |
—
|
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: polyethylene | Statement: [Marlex polyethylene, hasPolymerType, polyethylene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolymerType Context triple: [Marlex polyethylene, hasPolymerType, polyethylene]
-
A.
hasPolymerizationType
Indicates the specific kind of polymerization process or mechanism associated with an entity.
-
B.
polymerType
chosen
Indicates the specific kind or classification of polymer associated with an entity.
-
C.
introducedAsPolymer
Indicates that an entity was presented or launched specifically in the form of a polymer material or polymer-based product.
-
D.
isBasedOnMonomer
Indicates that one entity is derived from, constructed from, or fundamentally determined by a specific monomer unit.
-
E.
isThermoplastic
Indicates that a material softens when heated and hardens when cooled in a reversible, repeatable way without undergoing a permanent chemical change.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: May 3, 2026, 4:06 p.m.