Triple
T8286240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solitaire |
E193792
|
entity |
| Predicate | teachesInteractionConcept |
P21344
|
FINISHED |
| Object | drag and drop |
—
|
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: drag and drop | Statement: [Solitaire, teachesInteractionConcept, drag and drop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teachesInteractionConcept Context triple: [Solitaire, teachesInteractionConcept, drag and drop]
-
A.
trainingConcept
Indicates that one entity serves as a concept, topic, or subject matter that is being taught or trained on in relation to another entity.
-
B.
teachesAbout
chosen
Indicates that one entity provides instruction or information to another entity on a particular subject or topic.
-
C.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
D.
demonstratedConcept
Indicates that an entity has shown, illustrated, or made evident a particular concept through example, explanation, or action.
-
E.
interactionWithHumans
Indicates a relationship where an entity engages in some form of contact, communication, or mutual influence with humans.
- 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.