Triple
T14343332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Play Framework |
E355654
|
entity |
| Predicate | uses |
P98
|
FINISHED |
| Object | Akka |
E355653
|
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: Akka | Statement: [Play Framework, uses, Akka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Akka Context triple: [Play Framework, uses, Akka]
-
A.
Akka
Akka is an alternative name for Acre, a historic port city in present-day Israel known for its Crusader-era fortifications and diverse cultural heritage.
-
B.
Akka
chosen
Akka is a toolkit and runtime for building highly concurrent, distributed, and resilient message-driven applications on the JVM, widely used within the Scala ecosystem.
-
C.
Akrar
Akrar is a small village located on the island of Suðuroy in the Faroe Islands.
-
D.
Shuka
Shuka is a Japanese animation studio known for producing the later seasons and related works of the urban fantasy anime series Durarara!!.
-
E.
Oda
Oda is a Japanese samurai clan most famously associated with the powerful 16th-century warlord Oda Nobunaga, a key figure in the unification of Japan.
- 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_69fd469d899081909103563f209dd944 |
completed | May 8, 2026, 2:12 a.m. |
Created at: April 10, 2026, 1:14 a.m.