Triple
T29388895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3380 |
E745323
|
entity |
| Predicate | definesProtocolExtensionsFor |
P66718
|
FINISHED |
| Object | Internet Printing Protocol |
—
|
NE NERFINISHED |
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: Internet Printing Protocol | Statement: [RFC 3380, definesProtocolExtensionsFor, Internet Printing Protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesProtocolExtensionsFor Context triple: [RFC 3380, definesProtocolExtensionsFor, Internet Printing Protocol]
-
A.
specifiesProtocolExtensionFor
chosen
Indicates that one protocol extension defines or constrains the behavior, capabilities, or usage of another protocol.
-
B.
definesExtension
Indicates that one entity specifies or establishes the extension, scope, or detailed form of another entity.
-
C.
supportedProtocol
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
D.
definesInterfaceProtocol
Indicates that one entity specifies or establishes the communication or interaction protocol that another entity must follow as its interface.
-
E.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 28, 2026, 2:41 p.m.