Triple
T16492958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | fermium-252 |
E400609
|
entity |
| Predicate | requiresHandlingProtocol |
P64035
|
FINISHED |
| Object | remote handling techniques |
—
|
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: remote handling techniques | Statement: [fermium-252, requiresHandlingProtocol, remote handling techniques]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresHandlingProtocol Context triple: [fermium-252, requiresHandlingProtocol, remote handling techniques]
-
A.
associatedProtocol
chosen
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
-
B.
securesProtocol
Indicates that one entity protects, safeguards, or enforces the security of a communication or operational protocol for another entity.
-
C.
isProtocolAgnostic
Indicates that the relationship or mechanism functions independently of any specific communication protocol, working uniformly across different protocols.
-
D.
targetProtocol
Indicates the communication protocol that an action, message, or connection is intended to use or be directed toward.
-
E.
mustHandle
Indicates that one entity is required or obligated to process, deal with, or take responsibility for another entity or situation.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e30cb648190a52cb32896c4ac5a |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:13 a.m.