Triple
T8286239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solitaire |
E193792
|
entity |
| Predicate | wasUsedTo |
P98
|
FINISHED |
| Object | familiarize users with mouse operations |
—
|
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: familiarize users with mouse operations | Statement: [Solitaire, wasUsedTo, familiarize users with mouse operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasUsedTo Context triple: [Solitaire, wasUsedTo, familiarize users with mouse operations]
-
A.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
-
B.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
C.
usedOver
Indicates that one entity has been utilized, applied, or consumed in relation to another entity, typically as a resource, medium, or tool in a particular context or period.
-
D.
usedToWrite
Indicates that one entity served as a tool, medium, or instrument that another entity employed to perform the act of writing.
-
E.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad3722481908076508908d18621 |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:52 p.m.