Triple
T2318940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6176 |
E51131
|
entity |
| Predicate | obsoletesProtocolVersion |
P5977
|
FINISHED |
| Object | SSL 2.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: SSL 2.0 | Statement: [RFC 6176, obsoletesProtocolVersion, SSL 2.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obsoletesProtocolVersion Context triple: [RFC 6176, obsoletesProtocolVersion, SSL 2.0]
-
A.
protocolVersion
Indicates the specific version of a protocol that governs how two or more entities communicate or interact.
-
B.
specifiesProtocolVersion
Indicates that an entity defines or sets the particular protocol version to be used in a communication or interaction.
-
C.
previousVersionAdopted
chosen
Indicates that one entity has been adopted or implemented as a successor to an earlier version represented by the other entity.
-
D.
exportVersionOf
Indicates that one entity is a version of another specifically created or designated for export (e.g., for external distribution or use).
-
E.
exportVersion
Indicates the specific release or revision identifier of an item as it is prepared for or used in export.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc5909cc48190aab257313542dc49 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.