Triple
T34785154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin Defense |
E1002784
|
entity |
| Predicate | mainLineAfter |
P155506
|
FINISHED |
| Object | 1.e4 e5 2.Nf3 Nc6 3.Bb5 Nf6 4.0-0 Nxe4 |
—
|
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: 1.e4 e5 2.Nf3 Nc6 3.Bb5 Nf6 4.0-0 Nxe4 | Statement: [Berlin Defense, mainLineAfter, 1.e4 e5 2.Nf3 Nc6 3.Bb5 Nf6 4.0-0 Nxe4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainLineAfter Context triple: [Berlin Defense, mainLineAfter, 1.e4 e5 2.Nf3 Nc6 3.Bb5 Nf6 4.0-0 Nxe4]
-
A.
mainLine
Indicates that something serves as the primary or central line, route, or sequence among a set of related lines.
-
B.
mainLineCompleted
Indicates that the primary or central process, route, or sequence of steps has been fully finished or brought to completion.
-
C.
partOfMainLine
chosen
Indicates that something belongs to, or is a segment of, the primary or principal line within a larger system or structure.
-
D.
finalLine
Indicates that something is the last or concluding line in a sequence, text, or structured content.
-
E.
servesMainLine
Indicates that one entity functions as the primary or main service line for 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.