Triple
T5068452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loss of Control |
E114200
|
entity |
| Predicate | playContext |
P32813
|
FINISHED |
| Object | multiplayer card game |
—
|
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: multiplayer card game | Statement: [Loss of Control, playContext, multiplayer card game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playContext Context triple: [Loss of Control, playContext, multiplayer card game]
-
A.
playIn
chosen
Indicates that an entity participates or performs in a particular event, context, or location (such as a game, match, or venue).
-
B.
playerControl
Indicates that one entity (typically a player) has control or command over another entity or object within a system or environment.
-
C.
musicFocus
Indicates that the primary attention or emphasis is directed toward music or musical aspects.
-
D.
musicSource
Indicates that one entity serves as the origin or provider of music for another entity or context.
-
E.
playType
Indicates the specific category or style of play or performance associated with an event or action.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd749dd1a08190858fa739df024eb4 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.