Triple
T27750315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Backgammon |
E702097
|
entity |
| Predicate | hasRandomness |
P149868
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Backgammon, hasRandomness, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRandomness Context triple: [Backgammon, hasRandomness, high]
-
A.
isRandomized
Indicates that the selection, ordering, or assignment associated with something is determined by a random process rather than a fixed or predetermined rule.
-
B.
introducesRandomnessIn
chosen
Indicates that something adds an element of unpredictability or variability into another process, system, or outcome.
-
C.
canBeRandomized
Indicates that the entity is capable of having its state, order, or selection determined by a random process.
-
D.
hasRandomizedApproximation
Indicates that there exists a randomized algorithm or method that can approximate the result of the referenced entity or process within some probabilistic accuracy or error bounds.
-
E.
hasRandomizedAlgorithmBaseline
Indicates that an entity is associated with a baseline performance or reference result obtained using a randomized algorithm.
- 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_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 4:19 p.m.