Triple
T7106112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novichok nerve agent |
E165586
|
entity |
| Predicate | exposureRoute |
P52267
|
FINISHED |
| Object | inhalation |
—
|
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: inhalation | Statement: [Novichok nerve agent, exposureRoute, inhalation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposureRoute Context triple: [Novichok nerve agent, exposureRoute, inhalation]
-
A.
exposureType
Indicates the specific manner or context in which one entity is exposed to another entity, condition, or influence.
-
B.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
C.
exposesTo
Indicates that one entity subjects another entity to contact with or influence from something, typically involving risk, effect, or experience.
-
D.
providesExposureTo
Indicates that one entity gives another entity the opportunity to be seen, noticed, or become known by a particular audience, environment, or set of influences.
-
E.
routeOfExposure
chosen
Indicates the pathway or method by which an agent, substance, or factor comes into contact with or enters an organism or system.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5b892008190827fa1e5eab2e558 |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.