Triple
T32025325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anand Variation |
E817801
|
entity |
| Predicate | typicalPlanForWhite |
P70722
|
FINISHED |
| Object | central space advantage and pressure on d5 |
—
|
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: central space advantage and pressure on d5 | Statement: [Anand Variation, typicalPlanForWhite, central space advantage and pressure on d5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPlanForWhite Context triple: [Anand Variation, typicalPlanForWhite, central space advantage and pressure on d5]
-
A.
hasTypicalPlan
chosen
Indicates that there is a standard or commonly followed plan, procedure, or course of action typically associated with the given entity or situation.
-
B.
plannedVia
Indicates that something is arranged, organized, or scheduled by means of a particular method, process, or intermediary.
-
C.
bodyPlan
Indicates the overall structural organization and arrangement of an organism’s body, including the layout and relationship of its major parts.
-
D.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
E.
partOfPlan
Indicates that one entity is included as a component or step within a broader plan or strategy.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:17 a.m.