Triple
T3081857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF working groups |
E64275
|
entity |
| Predicate | example |
P1259
|
FINISHED |
| Object | TLS Working Group |
E184134
|
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 Working Group | Statement: [IETF working groups, example, TLS Working Group]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TLS Working Group Context triple: [IETF working groups, example, TLS Working Group]
-
A.
TLS Working Group
chosen
The TLS Working Group is an IETF group responsible for developing and maintaining the Transport Layer Security (TLS) protocol and related technologies that secure communications over computer networks.
-
B.
HTTP Working Group
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
-
C.
IETF working groups
IETF working groups are collaborative teams of experts within the Internet Engineering Task Force that develop and standardize technical specifications and protocols for the Internet.
-
D.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
-
E.
GNSO Working Groups
GNSO Working Groups are collaborative teams within ICANN’s Generic Names Supporting Organization that develop and refine policies related to generic top-level domains through open, consensus-driven processes.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1e70b9081908c801d084a6ae992 |
completed | March 8, 2026, 4:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1f89847e48190b82849701e119758 |
completed | March 11, 2026, 11:19 p.m. |
Created at: March 8, 2026, 3:03 p.m.