Triple
T14740029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3652 |
E346320
|
entity |
| Predicate | specifies |
P773
|
FINISHED |
| Object | Handle System protocols |
E1105287
|
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 protocols | Statement: [RFC 3652, specifies, Handle System protocols]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Handle System protocols Context triple: [RFC 3652, specifies, Handle System protocols]
-
A.
Handle protocol
chosen
The Handle protocol is a distributed system for assigning, managing, and resolving persistent identifiers for digital objects on the internet.
-
B.
Handle System
The Handle System is a global, distributed identifier system designed to provide persistent, secure, and scalable resolution of digital object identifiers on the internet.
-
C.
worldwide Handle System
The worldwide Handle System is a global infrastructure for assigning, managing, and resolving persistent identifiers for digital objects across distributed networks.
-
D.
Building Protocols with HTTP
"Building Protocols with HTTP" is an IETF document (RFC 9205) that provides guidance and best practices for designing application protocols that use HTTP as a substrate.
-
E.
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.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7345680819093e901233a064e48 |
completed | April 14, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb91fdf88190bdcc9a93289f6b7f |
completed | May 8, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:30 a.m.