Triple
T5480533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSS |
E123455
|
entity |
| Predicate | protocolUsedOnInterface |
P31215
|
FINISHED |
| Object | Diameter |
—
|
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: Diameter | Statement: [HSS, protocolUsedOnInterface, Diameter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protocolUsedOnInterface Context triple: [HSS, protocolUsedOnInterface, Diameter]
-
A.
protocolName
chosen
Indicates the specific communication or interaction protocol used or associated with an entity or connection.
-
B.
protocolNumber
Indicates the specific identifying number assigned to a protocol that governs or documents an interaction, process, or agreement between entities.
-
C.
protocolLayer
Indicates a relationship where a communication protocol operates at, or is associated with, a specific layer in a protocol stack or network architecture.
-
D.
protocolBinding
Indicates that one protocol is bound or mapped to another protocol or transport mechanism for communication or interoperability purposes.
-
E.
protocolFullName
Indicates that one entity is the complete, human-readable name of a protocol associated with another entity.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9248ca348190aa116cace0f9b07a |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.