Triple
T8482426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go |
E200551
|
entity |
| Predicate | chanceElements |
P76195
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Go, chanceElements, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chanceElements Context triple: [Go, chanceElements, none]
-
A.
chanceElement
chosen
Indicates that the relationship or outcome involves randomness or probabilistic chance rather than being deterministic.
-
B.
usesElementsOf
Indicates that one entity incorporates, applies, or draws upon components, principles, or features derived from another entity.
-
C.
gameElement
Indicates that one entity functions as a component, feature, or part within the structure or mechanics of a game.
-
D.
mixesElementsOf
Indicates a relationship where one entity combines or blends components, features, or aspects of another entity or set of entities into a unified whole.
-
E.
holdsAlmostSurely
Indicates that the specified property or event occurs with probability 1, i.e., it is true almost everywhere except possibly on a set of outcomes of probability zero.
- 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53638c48190b742fc51d1b4442a |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.