Triple
T8245159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nylon |
E192833
|
entity |
| Predicate | hasPolymerizationType |
P81132
|
FINISHED |
| Object | condensation polymerization |
—
|
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: condensation polymerization | Statement: [Nylon, hasPolymerizationType, condensation polymerization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolymerizationType Context triple: [Nylon, hasPolymerizationType, condensation polymerization]
-
A.
hasHybridization
Indicates that one entity participates in or results from a hybridization process involving another entity.
-
B.
hasBondType
Indicates the specific kind of bond or connection that exists between two related entities.
-
C.
hasFormulationType
Indicates the specific way something is physically prepared or presented, such as its dosage form, composition, or delivery format.
-
D.
hasParticleType
Indicates that an entity is associated with, composed of, or characterized by a specific type or category of particle.
-
E.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
- 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.