Triple
T22375088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balderdash |
E553132
|
entity |
| Predicate | maintains |
P1580
|
FINISHED |
| Object | Sails.js |
—
|
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: Sails.js | Statement: [Balderdash, maintains, Sails.js]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sails.js Context triple: [Balderdash, maintains, Sails.js]
-
A.
Sails.js
chosen
Sails.js is a Node.js MVC framework designed for building data-driven, real-time web applications with a structure similar to frameworks like Ruby on Rails.
-
B.
FeathersJS
FeathersJS is a lightweight, real-time microservices framework for Node.js that simplifies building REST and WebSocket APIs.
-
C.
Express.js
Express.js is a minimalist and flexible Node.js web application framework used to build APIs and server-side applications.
-
D.
Balderdash (Sails.js creators)
Balderdash is the software development company best known for creating the Sails.js web framework and its associated ORM, Waterline.
-
E.
Ember.js
Ember.js is an open-source JavaScript framework for building ambitious, large-scale web applications using a convention-over-configuration approach.
- 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.