Triple
T5421587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 768 |
E121262
|
entity |
| Predicate | definesProtocolFor |
P12564
|
FINISHED |
| Object | application-level protocols |
—
|
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: application-level protocols | Statement: [RFC 768, definesProtocolFor, application-level protocols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesProtocolFor Context triple: [RFC 768, definesProtocolFor, application-level protocols]
-
A.
specifiesProtocol
chosen
Indicates that one entity defines or designates the communication or interaction protocol to be used by another entity.
-
B.
supportedProtocol
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
C.
targetsProtocol
Indicates that one entity is designed to interact with, affect, or be applied to a specific protocol.
-
D.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
E.
encapsulatesProtocol
Indicates that one entity implements and contains the functionality of a specific communication or interaction protocol on behalf of 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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87eac41481908a4982db5d119edd |
completed | March 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.