Triple
T1613096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NestJS |
E34654
|
entity |
| Predicate | developer |
P73
|
FINISHED |
| Object | NestJS core team |
E34654
|
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: NestJS core team | Statement: [NestJS, developer, NestJS core team]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NestJS core team Context triple: [NestJS, developer, NestJS core team]
-
A.
NestJS
chosen
NestJS is a progressive Node.js framework for building efficient, scalable server-side applications using TypeScript and a modular, dependency-injection-driven architecture.
-
B.
npm, Inc.
npm, Inc. is the company behind the npm package manager and registry, a central infrastructure provider for JavaScript and Node.js developers.
-
C.
Nuxt.js
Nuxt.js is a high-level framework built on Vue.js that simplifies the development of server-rendered, statically generated, and single-page web applications.
-
D.
Python core developers
Python core developers are the group of trusted contributors responsible for designing, implementing, and maintaining the official Python language and its reference implementation.
-
E.
FeathersJS
FeathersJS is a lightweight, real-time microservices framework for Node.js that simplifies building REST and WebSocket APIs.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9098e245c8190b0169b648434aa49 |
completed | March 5, 2026, 4:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad51c751308190a89f6462ee365418 |
completed | March 8, 2026, 10:39 a.m. |
Created at: March 4, 2026, 7:28 p.m.