Triple

T22374947
Position Surface form Disambiguated ID Type / Status
Subject koa-bodyparser E553128 entity
Predicate relatedTo P37 FINISHED
Object koa-router 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-router | Statement: [koa-bodyparser, relatedTo, koa-router]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: koa-router
Context triple: [koa-bodyparser, relatedTo, koa-router]
  • A. koa-router chosen
    koa-router is a popular routing middleware for the Koa web framework that provides URL routing, route parameters, and middleware composition for building Node.js APIs and web applications.
  • B. Cofiroute
    Cofiroute is a French toll road concession company that finances, builds, and operates motorway and tunnel infrastructure.
  • C. React Router
    React Router is a popular routing library for React applications that enables declarative, client-side navigation and URL management in single-page apps.
  • D. Koa web framework
    Koa is a minimalist, modern Node.js web framework designed by TJ Holowaychuk to provide a smaller, more expressive, and robust foundation for web applications and APIs using async functions.
  • E. Preact Router
    Preact Router is a lightweight routing library designed to handle client-side navigation in Preact single-page applications.
  • 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_69f15807cb748190abd9adc08ca1ad4f completed April 29, 2026, 12:59 a.m.
Created at: April 16, 2026, 8:45 p.m.