Triple

T17677547
Position Surface form Disambiguated ID Type / Status
Subject OTP E440676 entity
Predicate maintainer P2962 FINISHED
Object Erlang/OTP team at Ericsson 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: Erlang/OTP team at Ericsson | Statement: [OTP, maintainer, Erlang/OTP team at Ericsson]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Erlang/OTP team at Ericsson
Context triple: [OTP, maintainer, Erlang/OTP team at Ericsson]
  • A. Erlang/OTP team chosen
    The Erlang/OTP team is the group at Ericsson responsible for developing and maintaining the Erlang programming language and its Open Telecom Platform (OTP) libraries and runtime system.
  • B. Elixir Core Team
    The Elixir Core Team is the group of maintainers and lead contributors responsible for designing, developing, and stewarding the Elixir programming language and its ecosystem.
  • C. Microsoft .NET team
    The Microsoft .NET team is the group at Microsoft responsible for developing, evolving, and supporting the .NET platform and its ecosystem of tools, libraries, and frameworks.
  • D. Codership
    Codership is a software company best known for creating the Galera Cluster synchronous multi-master replication technology for MySQL and related databases.
  • E. RSpec core team
    The RSpec core team is the group of maintainers responsible for developing and overseeing the core components of the RSpec testing framework for Ruby.
  • 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_69d8b9e940b081908b862bb0e6e89b0d completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e46f6e959c819092d9d33e79bd51f7 completed April 19, 2026, 6 a.m.
Created at: April 10, 2026, 10:01 a.m.