Triple

T22374561
Position Surface form Disambiguated ID Type / Status
Subject TJ Holowaychuk E553120 entity
Predicate notableWork P4 FINISHED
Object Koa 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: Koa | Statement: [TJ Holowaychuk, notableWork, Koa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koa
Context triple: [TJ Holowaychuk, notableWork, Koa]
  • A. Koa chosen
    Koa is a lightweight, modern Node.js web framework designed by the creators of Express to provide a more expressive and robust foundation for web applications and APIs.
  • B. Kona
    Kona is a coastal town on the western side of Hawaii's Big Island, known for its coffee farms, historic sites, and popular snorkeling and diving spots.
  • C. Kona
    Kona is a locality in the Howrah district of West Bengal, India, known for its strategic position near major transport routes connecting to Kolkata.
  • D. Nuʻuuli
    Nuʻuuli is a village and commercial center on the island of Tutuila in American Samoa.
  • E. Punga
    Punga is a figure from Māori mythology, traditionally regarded as an ancestor of sharks, lizards, and other troublesome sea creatures.
  • 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_69e11e4c03248190a26a5060ea6973ee completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15806b534819083716c2b090ede42 completed April 29, 2026, 12:59 a.m.
Created at: April 16, 2026, 8:45 p.m.