Triple
T22814534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Media Source Extensions |
E565064
|
entity |
| Predicate | apiSurface |
P149839
|
FINISHED |
| Object | MediaSource.isTypeSupported() |
—
|
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: MediaSource.isTypeSupported() | Statement: [Media Source Extensions, apiSurface, MediaSource.isTypeSupported()]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apiSurface Context triple: [Media Source Extensions, apiSurface, MediaSource.isTypeSupported()]
-
A.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
B.
targetSurface
Indicates the surface or area that an action, effect, or object is directed at or intended to impact.
-
C.
surfaceRecord
Indicates that an entity documents or presents information about the external aspects or observable features of another entity or phenomenon.
-
D.
capSurface
Indicates that one entity serves as the top or end surface (a cap) enclosing or terminating another entity.
-
E.
usesSurface
Indicates that one entity employs or interacts with another entity as a surface or platform for its action or function.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d62b0ec8190ac22909192e8a876 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:33 p.m.