Triple

T18158192
Position Surface form Disambiguated ID Type / Status
Subject SHA-2 E434687 entity
Predicate usedIn P98 FINISHED
Object TLS 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: TLS | Statement: [SHA-2, usedIn, TLS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TLS
Context triple: [SHA-2, usedIn, TLS]
  • A. TLS chosen
    TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
  • B. TLS
    TLS is the IATA airport code for Toulouse-Blagnac Airport, the main international airport serving Toulouse in southwestern France.
  • C. TLS
    TLS is the ISO 3166-1 alpha-3 country code for Timor-Leste (East Timor), a Southeast Asian nation on the eastern half of Timor Island.
  • D. TLS
    TLS is the Australian Securities Exchange (ASX) stock ticker for Telstra, Australia's largest telecommunications and media company.
  • E. SSL
    SSL is a satellite manufacturing company known for building commercial communications and Earth observation spacecraft.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b90b7a188190b3fc7b8d4a6cd20a completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4dec02d9c81909ac6203b7d59c405 completed April 19, 2026, 1:55 p.m.
Created at: April 10, 2026, 10:30 a.m.