Triple
T35208804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ScrollToOptions |
E1016613
|
entity |
| Predicate | behaviorDefaultValue |
P33686
|
FINISHED |
| Object | auto |
—
|
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: auto | Statement: [ScrollToOptions, behaviorDefaultValue, auto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: behaviorDefaultValue Context triple: [ScrollToOptions, behaviorDefaultValue, auto]
-
A.
defaultValue
Indicates that one entity serves as the pre-assigned or fallback value automatically used for another entity when no explicit value is provided.
-
B.
defaultBehavior
chosen
Indicates the standard or fallback way an entity acts or responds when no specific or overriding instructions or conditions are provided.
-
C.
privateBehavior
Indicates behavior or actions that are intended to be kept confidential, hidden, or restricted from public or general observation.
-
D.
behaviorCode
Indicates the specific rule, standard, or classification code that governs or characterizes an entity’s behavior in a given context.
-
E.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to another entity.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.