Triple
T30065774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CUDA Runtime API |
E764026
|
entity |
| Predicate | typicalCallPrefix |
P204200
|
FINISHED |
| Object | cuda |
—
|
LITERAL 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: cuda | Statement: [CUDA Runtime API, typicalCallPrefix, cuda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCallPrefix Context triple: [CUDA Runtime API, typicalCallPrefix, cuda]
-
A.
nationalPrefixForDomesticCalls
Indicates the dialing prefix that must be used when making domestic telephone calls within a given country or numbering plan.
-
B.
mobileNumberPrefix
Indicates that one entity is a telephone number prefix associated with, or used to begin, the other entity’s mobile phone numbers.
-
C.
callingCode
Indicates the telephone country or area code associated with an entity for making phone calls.
-
D.
callingCodeType
Indicates the type or category of a telephone calling code associated with an entity.
-
E.
tollFreePrefixExample
Indicates that the subject is an example of a telephone number prefix that designates a toll-free calling number.
- F. None of above. chosen
Provenance (4 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0346b487088190814e4bd0765cb609 |
completed | May 12, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_6a0346428c60819090e5ea815c0921ca |
completed | May 12, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_6a0346b3b2708190b713ce3dfee1734a |
completed | May 12, 2026, 3:26 p.m. |
Created at: April 29, 2026, 6:59 p.m.