Triple
T26959240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Alekhine |
E678990
|
entity |
| Predicate | notableOpeningContribution |
P477
|
FINISHED |
| Object | Alekhine Defense |
—
|
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: Alekhine Defense | Statement: [Alexander Alekhine, notableOpeningContribution, Alekhine Defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOpeningContribution Context triple: [Alexander Alekhine, notableOpeningContribution, Alekhine Defense]
-
A.
notableContribution
chosen
Indicates that an entity has made a significant, recognized contribution to another entity, field, work, or endeavor.
-
B.
notableContributionField
Indicates the field or domain in which an entity has made a significant or noteworthy contribution.
-
C.
notableOpening
Indicates that an entity is particularly recognized or distinguished for its opening section, move, scene, or initial part.
-
D.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
notableImpactOn
Indicates that one entity has had a significant, recognizable, or influential effect on 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
Created at: April 27, 2026, 6:29 a.m.