Triple
T33435563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Share API |
E856230
|
entity |
| Predicate | featureDetectableVia |
P84759
|
FINISHED |
| Object | "navigator.share" in navigator |
—
|
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: "navigator.share" in navigator | Statement: [Web Share API, featureDetectableVia, "navigator.share" in navigator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureDetectableVia Context triple: [Web Share API, featureDetectableVia, "navigator.share" in navigator]
-
A.
detectorCapability
Indicates that one entity has the ability or functional capacity to detect, sense, or identify another entity or phenomenon.
-
B.
featuresAbility
chosen
Indicates that one entity possesses, includes, or provides a particular ability or capability associated with another entity.
-
C.
featuresMode
Indicates that one entity operates in, supports, or is characterized by a particular mode or configuration specified by another entity.
-
D.
featuresDemon
Indicates that an entity includes, depicts, or prominently involves a demon.
-
E.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
- 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_6a01b3af7b908190b4675c85d32d106c |
completed | May 11, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_6a01b35813c081908e484b2b9ca5dd05 |
completed | May 11, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:36 a.m.