Triple
T17477313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thelyphonida |
E425572
|
entity |
| Predicate | usesChemical |
P41178
|
FINISHED |
| Object | acetic acid |
—
|
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: acetic acid | Statement: [Thelyphonida, usesChemical, acetic acid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesChemical Context triple: [Thelyphonida, usesChemical, acetic acid]
-
A.
usesChemistry
Indicates that one entity applies or relies on chemistry, chemical methods, or chemical principles in relation to another entity or context.
-
B.
containsChemical
Indicates that one entity includes or has within it a specified chemical substance.
-
C.
usedSubstance
chosen
Indicates that an entity has consumed, applied, or otherwise made use of a particular substance.
-
D.
chemicallyRelatedTo
Indicates a relationship where two entities are connected through a chemical association, such as sharing structural features, participating in related reactions, or being derivable from one another chemically.
-
E.
keyChemicalDiscussed
Indicates that a particular chemical substance is a central topic of discussion in a given context or communication.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451bc3f908190b2c7a2d1f75a43f2 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.