Triple
T27750342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Backgammon |
E702097
|
entity |
| Predicate | isOftenPlayedFor |
P163204
|
FINISHED |
| Object | match points |
—
|
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: match points | Statement: [Backgammon, isOftenPlayedFor, match points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenPlayedFor Context triple: [Backgammon, isOftenPlayedFor, match points]
-
A.
isOftenPlayedFor
chosen
Indicates that one entity is frequently performed, used, or presented for the benefit, enjoyment, or experience of another entity.
-
B.
keyOftenPlayedIn
Indicates that a particular musical key is frequently used or performed in association with a given piece, artist, or context.
-
C.
isTypicallyPlayed
Indicates that an activity, game, or sport is commonly engaged in or performed by a particular type of participant or group.
-
D.
oftenPlayedDuring
Indicates that one thing (such as a song, piece, or media) is frequently played in the context, time, or situation associated with another.
-
E.
typicallyPlays
Indicates that an entity is most commonly or habitually associated with playing a particular role, instrument, position, or type of game.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 4:19 p.m.