Triple
T8245157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nylon |
E192833
|
entity |
| Predicate | hasTypicalMonomer |
P63642
|
FINISHED |
| Object | hexamethylenediamine |
—
|
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: hexamethylenediamine | Statement: [Nylon, hasTypicalMonomer, hexamethylenediamine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalMonomer Context triple: [Nylon, hasTypicalMonomer, hexamethylenediamine]
-
A.
hasTypicalSequence
Indicates that there is a usual or commonly occurring order or progression in which the related entities or events take place.
-
B.
hasMolecularWeight
Indicates that an entity possesses a specific molecular weight value, typically expressed in standardized units such as daltons or g/mol.
-
C.
hasSubunits
Indicates that an entity is composed of or organized into smaller constituent units that are part of its structure.
-
D.
hasBasicUnit
chosen
Indicates that one entity is composed of, defined by, or fundamentally characterized through another entity that serves as its basic or minimal unit.
-
E.
hasMajorComponent
Indicates that one entity includes another entity as a primary or most significant component or part.
- 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_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. |
Created at: March 30, 2026, 5:48 p.m.