Triple
T30337919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XBoard/WinBoard protocol |
E771670
|
entity |
| Predicate | supportsVariants |
P38601
|
FINISHED |
| Object | standard chess |
—
|
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: standard chess | Statement: [XBoard/WinBoard protocol, supportsVariants, standard chess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVariants Context triple: [XBoard/WinBoard protocol, supportsVariants, standard chess]
-
A.
supportsModelVariant
chosen
Indicates that one entity is capable of operating with, being compatible with, or otherwise accommodating a specific variant of a model.
-
B.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
C.
supportsSymmetricVariant
Indicates that one entity is compatible with or enables the use of a symmetric (mirrored or bidirectional) variant of another entity or feature.
-
D.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
E.
extendedVariantUsedFor
Indicates that one entity is an extended or modified variant that is used in place of, or for the purposes of, another entity.
- 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_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:54 p.m.