Triple
T23284133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No-Limit Texas Hold'em |
E588942
|
entity |
| Predicate | allowsMove |
P47595
|
FINISHED |
| Object | all-in |
—
|
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: all-in | Statement: [No-Limit Texas Hold'em, allowsMove, all-in]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsMove Context triple: [No-Limit Texas Hold'em, allowsMove, all-in]
-
A.
usesMove
Indicates that an entity performs or executes a specific move or action.
-
B.
commonMove
Indicates that two or more entities share the same movement or relocation event, occurring together or in an identical manner.
-
C.
movementSupported
chosen
Indicates that an entity’s movement is enabled, facilitated, or allowed by another entity or system.
-
D.
allowsTransferTo
Indicates that one entity permits or enables the transfer of something (such as rights, funds, or data) to another specified entity.
-
E.
usesMovement
Indicates that an entity performs or involves some form of movement as part of its action or behavior.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196454b4c8190a797537ce8912241 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:58 p.m.