Triple
T8245406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyvek |
E192837
|
entity |
| Predicate | recyclingCategory |
P81144
|
FINISHED |
| Object | plastic recycling stream |
—
|
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: plastic recycling stream | Statement: [Tyvek, recyclingCategory, plastic recycling stream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recyclingCategory Context triple: [Tyvek, recyclingCategory, plastic recycling stream]
-
A.
recyclingRecommended
Indicates that it is advised or preferable for the referenced item or material to be recycled rather than discarded by other means.
-
B.
typeOfWasteCovered
Indicates the specific category or kind of waste material that is included or addressed within a given context, agreement, or regulation.
-
C.
materialReusedAt
Indicates that some or all of a material is used again at a specified location or facility.
-
D.
hasTrashReceptacles
Indicates that one entity provides, contains, or is equipped with trash receptacles for waste disposal in relation to another entity or location.
-
E.
wasteOrigin
Indicates that one entity is the original source or point of generation of a particular waste associated with 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7872f6d481909ea1d3c2aad1a2b1 |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb447c146081909decf97bbd26c496 |
completed | March 31, 2026, 3:50 a.m. |
Created at: March 30, 2026, 5:48 p.m.