Triple
T27885530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Checkers |
E705212
|
entity |
| Predicate | usesPlayableSquares |
P85056
|
FINISHED |
| Object | dark squares only |
—
|
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: dark squares only | Statement: [Checkers, usesPlayableSquares, dark squares only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPlayableSquares Context triple: [Checkers, usesPlayableSquares, dark squares only]
-
A.
hasNumberOfSquares
Indicates that an entity is associated with a specific count of squares it contains or comprises.
-
B.
hasCheckOnKings
Indicates that one player’s move currently places the opposing king in check.
-
C.
usesPlayingArea
chosen
Indicates that one entity makes use of a particular playing area as the space in which an activity or event takes place.
-
D.
playableSide
Indicates that a particular side, faction, or team in a game can be actively controlled or chosen by the player.
-
E.
possiblePosition
Indicates that a given location or arrangement is a valid or allowable position for the entity within the specified context or constraints.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 6:32 p.m.