Triple
T18008357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenAI API platform |
E430811
|
entity |
| Predicate | dashboardURL |
P6055
|
FINISHED |
| Object | https://platform.openai.com |
—
|
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 | Statement: [OpenAI API platform, dashboardURL, https://platform.openai.com]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dashboardURL Context triple: [OpenAI API platform, dashboardURL, https://platform.openai.com]
-
A.
accessURL
chosen
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
-
B.
developerPortal
Indicates a relationship where an entity serves as or is associated with a centralized online interface or platform used by developers to access tools, documentation, and resources.
-
C.
registryURL
Indicates the web address where an entity’s official registration information is stored or can be accessed.
-
D.
developmentAffiliateFor
Indicates that one entity serves as a development-related affiliate, partner, or associated organization for another entity.
-
E.
hadURL
Indicates that an entity was associated with or linked to a specific URL at some point in time.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b51d44088190bfcd35e532a4c02a |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:24 a.m.