Triple
T1724706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2246 |
E37470
|
entity |
| Predicate | definesProtocolVersion |
P11574
|
FINISHED |
| Object | TLS 1.0 |
—
|
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: TLS 1.0 | Statement: [RFC 2246, definesProtocolVersion, TLS 1.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesProtocolVersion Context triple: [RFC 2246, definesProtocolVersion, TLS 1.0]
-
A.
specifiesProtocolVersion
chosen
Indicates that an entity defines or sets the particular protocol version to be used in a communication or interaction.
-
B.
protocolVersion
Indicates the specific version of a protocol that governs how two or more entities communicate or interact.
-
C.
specifiesProtocol
Indicates that one entity defines or designates the communication or interaction protocol to be used by another entity.
-
D.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
E.
protocolNumber
Indicates the specific identifying number assigned to a protocol that governs or documents an interaction, process, or agreement between entities.
- 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_69a8861acab88190bb43cde203429399 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aadb7bda1081908f2c41c520c9c55c |
completed | March 6, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69aa61c0a0288190bce9d60062a84b69 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.