Triple
T33435030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Screen Orientation API |
E856219
|
entity |
| Predicate | notFullySupportedIn |
P58067
|
FINISHED |
| Object | Some legacy desktop browsers |
—
|
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: Some legacy desktop browsers | Statement: [Screen Orientation API, notFullySupportedIn, Some legacy desktop browsers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notFullySupportedIn Context triple: [Screen Orientation API, notFullySupportedIn, Some legacy desktop browsers]
-
A.
notSupportedBy
Indicates that an entity does not receive assistance, endorsement, or backing from another entity.
-
B.
notFullyAdoptedIn
chosen
Indicates that something has not been completely or universally implemented, accepted, or put into practice within a specified context or domain.
-
C.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
D.
doNotSupport
Indicates that one entity withholds help, approval, or endorsement from another entity or action.
-
E.
notCompatibleWith
Indicates that two entities cannot function together properly or are unsuitable for joint use or interaction.
- 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.