Triple
T816310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FastAPI |
E17658
|
entity |
| Predicate | implements |
P1417
|
FINISHED |
| Object | ASGI specification |
E97055
|
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: ASGI specification | Statement: [FastAPI, implements, ASGI specification]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ASGI specification Context triple: [FastAPI, implements, ASGI specification]
-
A.
ASGI
chosen
ASGI (Asynchronous Server Gateway Interface) is a Python standard for asynchronous web servers and applications that enables high-performance, concurrent web frameworks and services.
-
B.
Gunicorn (with ASGI workers)
Gunicorn (with ASGI workers) is a Python WSGI/ASGI HTTP server that can run asynchronous web frameworks like FastAPI in a robust, production-ready environment.
-
C.
Uvicorn
Uvicorn is a high-performance, ASGI-compatible web server implementation for Python, commonly used to run modern async frameworks and applications.
-
D.
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.
-
E.
FastAPI
FastAPI is a modern, high-performance Python framework for building APIs with automatic interactive documentation and type hint–driven validation.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab621d2c819083f10bff4f66c482 |
completed | March 1, 2026, 9:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7928f8a808190aaf5f2a2f3ee676f |
completed | March 4, 2026, 2:01 a.m. |
Created at: March 1, 2026, 7:38 p.m.