Triple
T25929984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nim |
E653412
|
entity |
| Predicate | hasRuleVariant |
P2846
|
FINISHED |
| Object | misère play where the player who takes the last object loses |
—
|
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: misère play where the player who takes the last object loses | Statement: [Nim, hasRuleVariant, misère play where the player who takes the last object loses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuleVariant Context triple: [Nim, hasRuleVariant, misère play where the player who takes the last object loses]
-
A.
hasRule
chosen
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
B.
hasRuleFor
Indicates that one entity defines or applies a rule that governs or constrains another entity or situation.
-
C.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
D.
hasRuleOver
Indicates that one entity holds authority, control, or governance over another entity.
-
E.
hasVariantUsage
Indicates that an entity is used in an alternative or non-standard way compared to its primary or canonical usage.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60418322081908411c24d1dc820de |
completed | May 2, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 8:36 a.m.