Triple
T12335219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Grass Chemical Agent-Destruction Pilot Plant |
E294066
|
entity |
| Predicate | handlesAgent |
P104556
|
FINISHED |
| Object | sarin (GB) |
—
|
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: sarin (GB) | Statement: [Blue Grass Chemical Agent-Destruction Pilot Plant, handlesAgent, sarin (GB)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesAgent Context triple: [Blue Grass Chemical Agent-Destruction Pilot Plant, handlesAgent, sarin (GB)]
-
A.
hasAgent
Indicates that an action or event is carried out or initiated by a particular agent.
-
B.
supportsAgents
Indicates that one entity provides assistance, resources, or backing to agents so they can perform their roles or actions.
-
C.
handledWith
Indicates that an entity is managed, processed, or dealt with using a particular method, tool, or means.
-
D.
instrumentHandled
Indicates that an entity uses, operates, or physically manipulates an instrument or tool to perform an action or task.
-
E.
handlingProperty
Indicates that one entity specifies how another entity should be handled, processed, or treated under certain conditions.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f6683e881908920e1fee02a14e3 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93f607a88819089e89fd263ae9937 |
completed | April 10, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:53 p.m.