Triple

T4325730
Position Surface form Disambiguated ID Type / Status
Subject uWSGI E96630 entity
Predicate supportsProtocol P203 FINISHED
Object WSGI E129539 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: WSGI | Statement: [uWSGI, supportsProtocol, WSGI]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: WSGI
Context triple: [uWSGI, supportsProtocol, WSGI]
  • A. WSGI chosen
    WSGI (Web Server Gateway Interface) is a Python standard that defines a common interface between web servers and Python web applications or frameworks.
  • B. ASGI
    ASGI (Asynchronous Server Gateway Interface) is a Python standard for asynchronous web servers and applications that enables high-performance, concurrent web frameworks and services.
  • C. uWSGI
    uWSGI is a high-performance application server commonly used to run Python web applications in production, often sitting between web frameworks and web servers like Nginx.
  • D. mod_wsgi
    mod_wsgi is an Apache HTTP Server module that hosts Python-based web applications using the WSGI interface, commonly used to deploy frameworks like Flask and Django in production.
  • E. Flask
    Flask is a lightweight, flexible Python micro web framework designed for building web applications and APIs with minimal boilerplate.
  • 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_69b34542fd908190b11b08faad8decfd completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3513020f481909ff2fec3934f3002 completed March 12, 2026, 11:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5d09861a4819086a88bb42a8ea2e4 completed March 14, 2026, 9:18 p.m.
Created at: March 12, 2026, 11:13 p.m.