Triple
T8286248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solitaire |
E193792
|
entity |
| Predicate | isPlayableOn |
P72061
|
FINISHED |
| Object | physical tabletop |
—
|
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: physical tabletop | Statement: [Solitaire, isPlayableOn, physical tabletop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPlayableOn Context triple: [Solitaire, isPlayableOn, physical tabletop]
-
A.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
B.
playsOn
Indicates that one entity participates or performs on a particular team, platform, or medium.
-
C.
canAlsoBePlayedIn
chosen
Indicates that something (such as a game, media, or activity) is additionally playable or usable in another context, format, or environment beyond its primary one.
-
D.
playsInSystem
Indicates that an entity participates or operates within a particular system or framework.
-
E.
isUsedToPlay
Indicates that something serves as an instrument, tool, or medium for engaging in a game, sport, or other form of play.
- 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.