Triple
T14547440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Handle Registry |
E341324
|
entity |
| Predicate | basedOn |
P98
|
FINISHED |
| Object | Handle System protocol |
E68554
|
NE 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: Handle System protocol | Statement: [Global Handle Registry, basedOn, Handle System protocol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Handle System protocol Context triple: [Global Handle Registry, basedOn, Handle System protocol]
-
A.
Handle System
chosen
The Handle System is a global, distributed identifier system designed to provide persistent, secure, and scalable resolution of digital object identifiers on the internet.
-
B.
Handler
Handler is a surname most notably associated with Philip Handler, an influential American biochemist and former president of the U.S. National Academy of Sciences.
-
C.
OPRC-HNS Protocol
OPRC-HNS Protocol is an international maritime agreement that strengthens global preparedness and coordinated response to pollution incidents involving hazardous and noxious substances at sea.
-
D.
OUCH protocol
The OUCH protocol is a lightweight, low-latency electronic messaging protocol used by trading systems to submit, modify, and cancel orders directly on Nasdaq and other electronic markets.
-
E.
Handle-Body pattern
The Handle-Body pattern is a software design approach that separates an object’s public interface (“handle”) from its internal implementation and state (“body”) to enable encapsulation, flexibility, and easier maintenance.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb2ebdf9481909f4d2da1ad31099c |
completed | April 14, 2026, 9:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd7a6344b08190a3c1124c6dd7da96 |
completed | May 8, 2026, 5:53 a.m. |
Created at: April 10, 2026, 1:23 a.m.