Triple
T33435415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intersection Observer API |
E856227
|
entity |
| Predicate | hasPolyfills |
P198444
|
FINISHED |
| Object | Yes |
—
|
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 | Statement: [Intersection Observer API, hasPolyfills, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolyfills Context triple: [Intersection Observer API, hasPolyfills, Yes]
-
A.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
B.
hasSupported
Indicates that one entity has provided assistance, endorsement, or backing to another entity, either materially, emotionally, or through advocacy.
-
C.
hasLowSupportFor
Indicates that one entity provides insufficient or weak backing, endorsement, or assistance for another entity or proposition.
-
D.
hasPolicySupport
Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
-
E.
hasVendor
Indicates that an entity is supplied, serviced, or supported by a particular vendor or provider.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
| PDg | Predicate description generation | batch_69fee33485188190a43526c9d39e3b6a |
completed | May 9, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:36 a.m.