Triple

T22649664
Position Surface form Disambiguated ID Type / Status
Subject Ember.js E559059 entity
Predicate developer P73 FINISHED
Object Ember Core Team — NE NERFINISHED

How this triple was built (3 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: Ember Core Team | Statement: [Ember.js, developer, Ember Core Team]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Ember Core Team
Context triple: [Ember.js, developer, Ember Core Team]
  • A. 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.
  • B. Elm core team
    The Elm core team is the group of developers responsible for designing, maintaining, and evolving Elm’s official language features and core libraries.
  • C. Svelte core team
    The Svelte core team is the group of developers responsible for designing, maintaining, and advancing the Svelte framework and its official tooling.
  • D. Redux core team
    The Redux core team is the group of developers responsible for designing, maintaining, and evolving the Redux state management ecosystem and its official tools.
  • E. 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.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Ember Core Team
Target entity description: The Ember Core Team is the group of lead maintainers and decision-makers responsible for guiding the development, roadmap, and ecosystem of the Ember.js framework.
  • A. 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.
  • B. Elm core team
    The Elm core team is the group of developers responsible for designing, maintaining, and evolving Elm’s official language features and core libraries.
  • C. Svelte core team
    The Svelte core team is the group of developers responsible for designing, maintaining, and advancing the Svelte framework and its official tooling.
  • D. Redux core team
    The Redux core team is the group of developers responsible for designing, maintaining, and evolving the Redux state management ecosystem and its official tools.
  • E. 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.
  • F. None of above. chosen

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_69e245489dd88190b1f674acf61c8769 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1703b40b88190aec5cf2fa28bfcbf completed April 29, 2026, 2:43 a.m.
Created at: April 17, 2026, 3:05 p.m.