Triple

T7897949
Position Surface form Disambiguated ID Type / Status
Subject Redis E183380 entity
Predicate developer P73 FINISHED
Object Redis Ltd. E183380 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: Redis Ltd. | Statement: [Redis, developer, Redis Ltd.]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Redis Ltd.
Context triple: [Redis, developer, Redis Ltd.]
  • A. Redis chosen
    Redis is an in-memory data structure store commonly used as a database, cache, and message broker known for its high performance and low latency.
  • B. MongoDB Inc.
    MongoDB Inc. is a software company best known for developing the popular open-source NoSQL document database MongoDB, widely used for scalable, modern application development.
  • C. Jepsen
    Jepsen is a surname most notably associated with individuals such as display technology innovator Mary Lou Jepsen.
  • D. Nentego
    Nentego is the autonym of the Nanticoke people, an Indigenous group historically located in the Mid-Atlantic region of what is now the United States.
  • E. RethinkDB
    RethinkDB is an open-source, distributed NoSQL database designed for real-time applications by pushing live updates to clients as data changes.
  • 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_69ca828d13088190b222be7aa9f9315c completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a296db8819084c620b12f77acb5 completed March 31, 2026, 3:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5bb719a08190a0545a361f559bf7 completed March 31, 2026, 5:29 a.m.
Created at: March 30, 2026, 5:01 p.m.