Triple
T8482423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go |
E200551
|
entity |
| Predicate | captureRule |
P64241
|
FINISHED |
| Object | stones with no liberties are removed |
—
|
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: stones with no liberties are removed | Statement: [Go, captureRule, stones with no liberties are removed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captureRule Context triple: [Go, captureRule, stones with no liberties are removed]
-
A.
captureCondition
chosen
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
-
B.
compositionRule
Indicates how multiple elements or components are combined or arranged according to a specific rule or pattern.
-
C.
sanctioningRules
Indicates the rules or conditions under which sanctions or penalties are imposed in response to certain actions or behaviors.
-
D.
canFrameRules
Indicates that one entity is able to define or establish the governing rules or framework that apply to another entity or context.
-
E.
displayRule
Indicates the rule or condition that determines how something should be visually presented or displayed.
- 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.