Triple
T29035411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carbon QuickDraw APIs |
E737844
|
entity |
| Predicate | targetedLanguage |
P183492
|
FINISHED |
| Object | C |
—
|
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: C | Statement: [Carbon QuickDraw APIs, targetedLanguage, C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedLanguage Context triple: [Carbon QuickDraw APIs, targetedLanguage, C]
-
A.
targetLanguage
Indicates the language that is the intended recipient or focus of a communication, translation, or linguistic operation.
-
B.
targetsLanguage
chosen
Indicates that an action, resource, or entity is specifically directed toward, designed for, or intended to be used with a particular language.
-
C.
languageTargets
Indicates that a language is specifically directed at, intended for, or used to address a particular target entity (such as an audience, system, or domain).
-
D.
translationTargetLanguage
Indicates the language into which content is being or has been translated.
-
E.
linguisticTarget
Indicates that something serves as the specific linguistic element (such as a word, phrase, or expression) that is the focus or target of a given action, analysis, or relation.
- F. None of above.
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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 28, 2026, 9:58 a.m.