Triple

T7928852
Position Surface form Disambiguated ID Type / Status
Subject TLS Working Group E184134 entity
Predicate responsibleFor P636 FINISHED
Object TLS 1.1 E38039 NE 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.1 | Statement: [TLS Working Group, responsibleFor, TLS 1.1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TLS 1.1
Context triple: [TLS Working Group, responsibleFor, TLS 1.1]
  • A. TLS 1.1 chosen
    TLS 1.1 is an older version of the Transport Layer Security protocol that improved upon earlier SSL standards but has since been deprecated in favor of more secure versions like TLS 1.2 and 1.3.
  • B. TLS 1.0
    TLS 1.0 is an early version of the Transport Layer Security protocol used to secure communications over computer networks, now largely deprecated in favor of more secure later versions.
  • C. TLS 1.2
    TLS 1.2 is a widely deployed version of the Transport Layer Security protocol that provides encrypted and authenticated communication over computer networks.
  • D. SSL 3.0
    SSL 3.0 is an obsolete cryptographic protocol that once secured internet communications and served as the foundation for the early versions of TLS.
  • E. SSL 2.0
    SSL 2.0 is an early, now-obsolete version of the Secure Sockets Layer protocol that provided encrypted communication over networks before being replaced by more secure successors like TLS.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca828fe7bc819090f52c88dcd72183 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3ac9ac4c819082cd2190fc3ce5a2 completed March 31, 2026, 3:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69cbe011ccec8190ab60d18b761666af completed March 31, 2026, 2:54 p.m.
Created at: March 30, 2026, 5:07 p.m.