Triple
T27750346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Backgammon |
E702097
|
entity |
| Predicate | hasKnownVariants |
P455
|
FINISHED |
| Object | Acey-deucey |
—
|
NE NERFINISHED |
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: Acey-deucey | Statement: [Backgammon, hasKnownVariants, Acey-deucey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKnownVariants Context triple: [Backgammon, hasKnownVariants, Acey-deucey]
-
A.
hasVariant
chosen
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
B.
hasVariantIdentifications
Indicates that an entity is associated with one or more alternative identifications or versions that differ in some defined way from a primary identification.
-
C.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
D.
hasKeyVariants
Indicates that an entity is associated with one or more alternative key forms or versions that function as variants of a primary key.
-
E.
hasVariantSystem
Indicates that one system is an alternative or variant form of another system within the same general framework or category.
- 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_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 4:19 p.m.