Triple
T25533626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SteamVR |
E639987
|
entity |
| Predicate | API |
P36118
|
FINISHED |
| Object | OpenXR |
—
|
NE NERFINISHED |
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: OpenXR | Statement: [SteamVR, API, OpenXR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: API Context triple: [SteamVR, API, OpenXR]
-
A.
APIType
Indicates the type or category of an API associated with or used by an entity.
-
B.
APIName
chosen
Indicates the specific name or identifier assigned to an application programming interface (API) used to distinguish it from other APIs.
-
C.
applicationInterface
Indicates that one entity serves as an interface or interaction layer through which another entity accesses or uses an application’s functionality.
-
D.
apiStatus
Indicates the current operational state or condition of an API, such as whether it is available, degraded, or unavailable.
-
E.
APIGravity
Indicates a relationship where one API exerts a dominant or central influence over others, drawing integrations or dependencies toward it like a gravitational pull.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8652c908190bee57d3f2663e6b2 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 3:16 p.m.