Triple
T14343261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akka |
E355653
|
entity |
| Predicate | developer |
P73
|
FINISHED |
| Object | Lightbend |
E1094361
|
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: Lightbend | Statement: [Akka, developer, Lightbend]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lightbend Context triple: [Akka, developer, Lightbend]
-
A.
Lightbend
chosen
Lightbend is a software company best known for developing the Scala programming language ecosystem and reactive platforms such as the Akka toolkit for building scalable, distributed applications.
-
B.
Akka Toolkit
Akka Toolkit is a toolkit and runtime for building highly concurrent, distributed, and resilient message-driven applications on the JVM using the actor model.
-
C.
Akka HTTP
Akka HTTP is a toolkit for building asynchronous, high-performance HTTP-based services and clients on the JVM, leveraging Akka’s actor and streaming capabilities.
-
D.
Play Framework
Play Framework is a high-velocity, stateless web application framework for Java and Scala that emphasizes developer productivity and reactive, scalable architectures.
-
E.
Typesafe Akka
Typesafe Akka is the earlier branding of the Akka toolkit, a popular JVM-based framework for building highly concurrent, distributed, and resilient message-driven applications.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e89ed9c8190acdb647ee618e919 |
completed | April 14, 2026, 6:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c3f81e881909f742d0442e99dd6 |
completed | May 8, 2026, 2:36 a.m. |
Created at: April 10, 2026, 1:14 a.m.