Triple

T17675057
Position Surface form Disambiguated ID Type / Status
Subject Elixir Core Team E440623 entity
Predicate collaboratesWith P37 FINISHED
Object Elixir Core Contributors 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: Elixir Core Contributors | Statement: [Elixir Core Team, collaboratesWith, Elixir Core Contributors]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Elixir Core Contributors
Context triple: [Elixir Core Team, collaboratesWith, Elixir Core Contributors]
  • A. Elixir Core Team chosen
    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.
  • B. 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.
  • C. Erlang/OTP team
    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.
  • D. Ethereum core developers
    Ethereum core developers are the group of engineers and researchers responsible for designing, maintaining, and upgrading the Ethereum blockchain protocol.
  • E. Solidity core team
    The Solidity core team is the group of primary developers and maintainers responsible for designing, implementing, and evolving the Solidity smart contract programming language.
  • 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_69d8b9e87e18819087104a44dc4dc5b1 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e46f6cca54819094ea0bed1517724e completed April 19, 2026, 6 a.m.
Created at: April 10, 2026, 10 a.m.