Triple
T17597954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | actix-http |
E428622
|
entity |
| Predicate | usedBy |
P260
|
FINISHED |
| Object | Actix Web |
—
|
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: Actix Web | Statement: [actix-http, usedBy, Actix Web]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Actix Web Context triple: [actix-http, usedBy, Actix Web]
-
A.
actix-web
chosen
actix-web is a powerful, asynchronous web framework for the Rust programming language, known for its high performance and strong type safety.
-
B.
actix-http
actix-http is a low-level HTTP library in the Actix ecosystem that provides the core HTTP protocol handling and primitives used by the Actix Web framework.
-
C.
Actix ecosystem
The Actix ecosystem is a collection of high-performance Rust libraries and tools for building asynchronous web applications and services, centered around the Actix Web framework and its supporting components.
-
D.
actix-router
actix-router is the routing component of the Actix ecosystem, responsible for matching HTTP requests to the appropriate handlers in Rust web applications.
-
E.
actix-service
actix-service is a Rust library that provides a lightweight, composable service abstraction used as the foundation for building asynchronous middleware and request handling in the Actix ecosystem.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469ecfb108190a9e7a5b380f8ab93 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 5:51 a.m.