Triple
T30337941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chess960 |
E771671
|
entity |
| Predicate | startingPositionConstraint |
P81684
|
FINISHED |
| Object | bishops must be on opposite-colored squares |
—
|
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: bishops must be on opposite-colored squares | Statement: [Chess960, startingPositionConstraint, bishops must be on opposite-colored squares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingPositionConstraint Context triple: [Chess960, startingPositionConstraint, bishops must be on opposite-colored squares]
-
A.
initialPosition
Indicates the original or starting location of an entity before any movement or change in position occurs.
-
B.
initiatingPosition
Indicates the starting location or initial spatial position from which an action, process, or movement begins.
-
C.
positionRestriction
chosen
Indicates a constraint or limitation on where an entity may be located or positioned relative to something else.
-
D.
positionStartTime
Indicates the time at which a position, role, or placement begins.
-
E.
initiallyPositionedAs
Indicates that one entity’s starting or original position is specified relative to another entity or reference frame.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: April 29, 2026, 7:54 p.m.