Triple
T29482830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fetch API |
E747835
|
entity |
| Predicate | polyfillable |
P167224
|
FINISHED |
| Object | yes, via fetch polyfills for older 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: yes, via fetch polyfills for older browsers | Statement: [Fetch API, polyfillable, yes, via fetch polyfills for older browsers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: polyfillable Context triple: [Fetch API, polyfillable, yes, via fetch polyfills for older browsers]
-
A.
papabile
Indicates that an individual is considered a likely or plausible candidate to be elected pope.
-
B.
fillType
Indicates the manner or pattern in which an area, shape, or container is filled (e.g., solid, gradient, pattern, or other fill style).
-
C.
potentialForm
Indicates that an action is expressed in its potential form, meaning the subject has the ability or possibility to perform that action.
-
D.
mayBeFilledBy
Indicates that one entity has the potential or permission to be occupied, completed, or satisfied by another entity.
-
E.
partiallyFilledFor
Indicates that one entity is incompletely or partially filled in service of, or in relation to, another entity.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66bdbc7e88190a5fe93938d0cdc7c |
completed | May 2, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 4:05 p.m.