Triple
T8245161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nylon |
E192833
|
entity |
| Predicate | hasFunctionalGroup |
P81133
|
FINISHED |
| Object | amide group |
—
|
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: amide group | Statement: [Nylon, hasFunctionalGroup, amide group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionalGroup Context triple: [Nylon, hasFunctionalGroup, amide group]
-
A.
hasSubfieldGroup
Indicates that an entity includes or is associated with a specific subgroup of related subfields within its overall structure or domain.
-
B.
hasFocusGroup
Indicates that an entity is associated with or participates in a specific focus group for targeted discussion, feedback, or research.
-
C.
hasFunctionCategory
Indicates that something is associated with a particular functional category or role it performs.
-
D.
hasCoveringGroup
Indicates that one group serves as a covering group (typically a covering or universal covering in the group-theoretic sense) for another group.
-
E.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of 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.