Triple

T4530002
Position Surface form Disambiguated ID Type / Status
Subject Jeremy Ashkenas E106271 entity
Predicate notableWork P4 FINISHED
Object CoffeeScript E17652 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: CoffeeScript | Statement: [Jeremy Ashkenas, notableWork, CoffeeScript]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CoffeeScript
Context triple: [Jeremy Ashkenas, notableWork, CoffeeScript]
  • A. CoffeeScript chosen
    CoffeeScript is a programming language that compiles to JavaScript, offering a more concise, Python- and Ruby-like syntax for writing web application code.
  • B. Moonscript
    Moonscript is a high-level programming language that compiles to Lua, offering a cleaner, more expressive syntax while targeting the Lua runtime.
  • C. PureScript
    PureScript is a strongly-typed, purely functional programming language that compiles to JavaScript and is heavily inspired by Haskell.
  • D. Haml
    Haml is a whitespace-sensitive templating language for Ruby that provides a clean, indentation-based syntax for generating HTML.
  • E. Elixir
    Elixir is a functional, concurrent programming language built on the Erlang VM, known for its scalability, fault tolerance, and expressive syntax.
  • 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_69bd43f3d6e08190a91824f833d51bbe completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd579ba4188190b4cef6e91772f7e5 completed March 20, 2026, 2:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdb9130b3c8190b511fa8a6ac0549b completed March 20, 2026, 9:16 p.m.
Created at: March 20, 2026, 1:03 p.m.