Triple
T30337949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chess960 |
E771671
|
entity |
| Predicate | castlingRule |
P168859
|
FINISHED |
| Object | castling results in standard chess castled positions |
—
|
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: castling results in standard chess castled positions | Statement: [Chess960, castlingRule, castling results in standard chess castled positions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castlingRule Context triple: [Chess960, castlingRule, castling results in standard chess castled positions]
-
A.
kingIsInviolable
Indicates that the king is protected from harm, violation, or infringement, often implying legal or moral immunity from certain actions.
-
B.
castleStatus
Indicates the current condition or state of a castle, such as whether it is intact, damaged, occupied, abandoned, or under construction.
-
C.
hasCheckOnKings
Indicates that one player’s move currently places the opposing king in check.
-
D.
centralKnight
Indicates that a knight is positioned near the center of the board or central area in the given context.
-
E.
servedKing
Indicates that one entity performed duties or services in allegiance or obedience to a king.
- F. None of above. chosen
Provenance (4 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f681ce34048190b4d31e2966949d8c |
completed | May 2, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 29, 2026, 7:54 p.m.