Triple
T805253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | API for Whisper |
E17415
|
entity |
| Predicate | documentationURL |
P6055
|
FINISHED |
| Object | https://platform.openai.com/docs |
—
|
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: https://platform.openai.com/docs | Statement: [API for Whisper, documentationURL, https://platform.openai.com/docs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentationURL Context triple: [API for Whisper, documentationURL, https://platform.openai.com/docs]
-
A.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
B.
accessURL
chosen
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
-
C.
linkedDocument
Indicates that one document is associated with or references another document in a meaningful way.
-
D.
doctypeSyntax
Indicates that one entity specifies or conforms to the syntax rules of a document type declaration (DOCTYPE) used in markup languages.
-
E.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ace495348190aec66f35ea90bc89 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa70973c8190adbf08302d1103a9 |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.