Triple

T18256886
Position Surface form Disambiguated ID Type / Status
Subject Tarantool Lua E437240 entity
Predicate tailoredFor P9494 FINISHED
Object Tarantool 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: Tarantool | Statement: [Tarantool Lua, tailoredFor, Tarantool]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tarantool
Context triple: [Tarantool Lua, tailoredFor, Tarantool]
  • A. ScyllaDB
    ScyllaDB is a high-performance, distributed NoSQL database designed as a drop-in replacement for Apache Cassandra, optimized for low latency and high throughput.
  • B. Tarantool Lua chosen
    Tarantool Lua is a specialized dialect of the Lua programming language tailored for the Tarantool in-memory database and application server, providing scripting and extension capabilities tightly integrated with its data and networking features.
  • C. VoltDB
    VoltDB is a high-performance, in-memory, distributed SQL database designed for real-time analytics and transaction processing at massive scale.
  • D. Percona
    Percona is an open-source database software and services company known for its performance-focused distributions and support for MySQL, MariaDB, MongoDB, and related technologies.
  • E. CockroachDB
    CockroachDB is a distributed SQL database designed for horizontal scalability, strong consistency, and high fault tolerance across multiple nodes and regions.
  • 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_69d8b913351c8190932b6a426de04b41 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4fd86e21081909c049082949b95c6 completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 10:34 a.m.