Triple
T27750325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Backgammon |
E702097
|
entity |
| Predicate | hasStandardDiceCountPerPlayer |
P190995
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Backgammon, hasStandardDiceCountPerPlayer, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardDiceCountPerPlayer Context triple: [Backgammon, hasStandardDiceCountPerPlayer, 2]
-
A.
hasStandardCheckerCountPerPlayer
Indicates the number of standard checkers that each player is assigned or expected to have.
-
B.
typicalNumberOfPlayers
Indicates the usual or standard number of players involved in participating in an activity or game.
-
C.
hasLeadCountPerSide
Indicates the number of lead elements or units associated with each side in a given context or configuration.
-
D.
dieSize
Indicates the size or number of faces of a die used in a game or randomization context.
-
E.
canBePlayedWithPhysicalCards
Indicates that the game or activity is playable using tangible, real-world physical cards rather than (or in addition to) digital or virtual formats.
- F. None of above. chosen
Provenance (4 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_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd866dd248190bff61c43bee93f54 |
completed | May 7, 2026, 6:22 p.m. |
Created at: April 27, 2026, 4:19 p.m.