Triple
T33435553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Share API |
E856230
|
entity |
| Predicate | level2Adds |
P110135
|
FINISHED |
| Object | file sharing support |
—
|
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: file sharing support | Statement: [Web Share API, level2Adds, file sharing support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: level2Adds Context triple: [Web Share API, level2Adds, file sharing support]
-
A.
level2Feature
Indicates that an entity possesses or is associated with a secondary or intermediate-level feature within a hierarchical feature structure.
-
B.
level1Feature
Indicates that one entity possesses or is associated with a primary or first-tier feature of another entity.
-
C.
level3Label
Indicates the third-level category or sublabel assigned to an entity within a hierarchical labeling or classification system.
-
D.
upperLevels
Indicates that one entity occupies or corresponds to higher levels, tiers, or hierarchical positions relative to another entity.
-
E.
laterAdditionsBy
chosen
Indicates that one entity consists of or represents additions or modifications that were made to another entity at a later time.
- 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_69f6e4857f3c819086399a37e954c6e9 |
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.