Triple
T22650416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remix Software |
E559075
|
entity |
| Predicate | maintains |
P1580
|
FINISHED |
| Object | React 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: React Router | Statement: [Remix Software, maintains, React Router]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: React Router Context triple: [Remix Software, maintains, React Router]
-
A.
React Router
chosen
React Router is a popular routing library for React applications that enables declarative, client-side navigation and URL management in single-page apps.
-
B.
Preact Router
Preact Router is a lightweight routing library designed to handle client-side navigation in Preact single-page applications.
-
C.
Vue Router
Vue Router is the official routing library for Vue.js applications, enabling client-side navigation, nested routes, and dynamic route matching.
-
D.
React Navigation
React Navigation is a popular JavaScript library for building navigators and managing in-app navigation in React Native applications.
-
E.
solidjs/solid-router
solidjs/solid-router is the official routing library for SolidJS applications, providing declarative, component-based navigation and route management.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703b40b88190aec5cf2fa28bfcbf |
completed | April 29, 2026, 2:43 a.m. |
Created at: April 17, 2026, 3:05 p.m.