Triple
T10068631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cuSPARSE |
E213160
|
entity |
| Predicate | supportsLanguage |
P2177
|
FINISHED |
| Object | C |
E9269
|
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: C | Statement: [cuSPARSE, supportsLanguage, C]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: C Context triple: [cuSPARSE, supportsLanguage, C]
-
A.
C
chosen
C is a foundational, general-purpose programming language known for its efficiency, low-level memory access, and influence on many later languages such as C++, Java, and Python.
-
B.
C
C is a local service on the New York City Subway that runs along the Eighth Avenue Line in Manhattan and continues through Brooklyn.
-
C.
C
C is a light rail service designation used by the Los Angeles Metro system for one of its primary rail lines.
-
D.
C
C is the New York Stock Exchange ticker symbol for Citigroup Inc., a major global financial services and banking corporation.
-
E.
C
C is the standard scholarly siglum for Codex Ephraemi Rescriptus, a 5th-century Greek biblical manuscript and palimpsest containing portions of the Old and New Testaments.
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcff8d9c08190bc030f1dcc696310 |
completed | April 2, 2026, 2:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d29a96fc888190aec7cd364a0d7fb1 |
completed | April 5, 2026, 5:23 p.m. |
Created at: March 30, 2026, 8:58 p.m.