Triple
T31593520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDX |
E806162
|
entity |
| Predicate | containsFunctionalGroup |
P81133
|
FINISHED |
| Object | nitramine 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: nitramine group | Statement: [RDX, containsFunctionalGroup, nitramine group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsFunctionalGroup Context triple: [RDX, containsFunctionalGroup, nitramine group]
-
A.
hasFunctionalGroup
chosen
Indicates that one chemical entity contains or is characterized by a specific functional group as part of its molecular structure.
-
B.
containsGroup
Indicates that one entity includes or encompasses a specific group of entities within it.
-
C.
addsFunctionalGroup
Indicates that one entity introduces or attaches a specific functional group to another entity.
-
D.
hasGroupStructure
Indicates that the related entities together form an algebraic group under a specified operation, satisfying closure, associativity, identity, and invertibility.
-
E.
containsFunction
Indicates that one entity includes, defines, or provides the implementation of a particular function.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
Created at: April 30, 2026, 10:29 p.m.