Triple
T25433526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kayles |
E637318
|
entity |
| Predicate | hasMoveRule |
P2846
|
FINISHED |
| Object | a player may remove one pin from the row |
—
|
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: a player may remove one pin from the row | Statement: [Kayles, hasMoveRule, a player may remove one pin from the row]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMoveRule Context triple: [Kayles, hasMoveRule, a player may remove one pin from the row]
-
A.
hasMoveType
Indicates that an action or move is associated with a specific type or category (such as elemental, functional, or classification-based).
-
B.
hasRule
chosen
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
C.
hasRuleOver
Indicates that one entity holds authority, control, or governance over another entity.
-
D.
hasRuleFor
Indicates that one entity defines or applies a rule that governs or constrains another entity or situation.
-
E.
hasMovementVariant
Indicates that one movement is an alternative or variant form of another movement.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 1:59 p.m.