Triple
T32025319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anand Variation |
E817801
|
entity |
| Predicate | hasOpeningFamily |
P185229
|
FINISHED |
| Object | Queen's Gambit Declined |
—
|
NE NERFINISHED |
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: Queen's Gambit Declined | Statement: [Anand Variation, hasOpeningFamily, Queen's Gambit Declined]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningFamily Context triple: [Anand Variation, hasOpeningFamily, Queen's Gambit Declined]
-
A.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
B.
hasFamilyBranch
Indicates that one entity is a subdivision, offshoot, or branch within the broader family group or lineage of another entity.
-
C.
hasOpeningMovement
Indicates that a work, performance, or sequence includes a distinct initial movement or section that begins the overall piece.
-
D.
hasOpenedFor
Indicates that one entity has performed or appeared as the opening act or preliminary participant for another entity, typically in an event or performance context.
-
E.
hasOpeningType
Indicates that one entity has, features, or is characterized by a particular type or kind of opening.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: May 1, 2026, 12:17 a.m.