Triple
T35208818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ScrollToOptions |
E1016613
|
entity |
| Predicate | scrollOrigin |
P182609
|
FINISHED |
| Object | top-left corner of the scrollable area |
—
|
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: top-left corner of the scrollable area | Statement: [ScrollToOptions, scrollOrigin, top-left corner of the scrollable area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scrollOrigin Context triple: [ScrollToOptions, scrollOrigin, top-left corner of the scrollable area]
-
A.
scrollPosition
Indicates the current vertical or horizontal offset of a scrollable container relative to its starting position.
-
B.
scrollingDirection
Indicates the direction in which a scrolling action is performed or is occurring between elements or within a view.
-
C.
scrollingType
Indicates the manner or mode in which scrolling is performed or behaves in a given context.
-
D.
depthOrigin
Indicates the reference point or source location from which the depth of an object or region is measured.
-
E.
hasScroll
Indicates that an entity possesses, contains, or is associated with a scroll.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.