Triple
T33434826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Bluetooth API |
E856215
|
entity |
| Predicate | notWidelySupportedBy |
P13137
|
FINISHED |
| Object | Mozilla Firefox |
—
|
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: Mozilla Firefox | Statement: [Web Bluetooth API, notWidelySupportedBy, Mozilla Firefox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notWidelySupportedBy Context triple: [Web Bluetooth API, notWidelySupportedBy, Mozilla Firefox]
-
A.
notSupportedBy
Indicates that an entity does not receive assistance, endorsement, or backing from another entity.
-
B.
notWidelyAcceptedSince
Indicates that something has not gained broad recognition, approval, or adoption from a specified time onward.
-
C.
notFullyAdoptedIn
Indicates that something has not been completely or universally implemented, accepted, or put into practice within a specified context or domain.
-
D.
notWellDocumented
Indicates that the subject lacks sufficient, clear, or comprehensive documentation.
-
E.
notImplementedBy
chosen
Indicates that a specified functionality, specification, or feature is *not* realized or provided by the referenced entity (such as a system, component, or implementation).
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e483f0f48190b38bbb7d0d335c2e |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.