Triple
T34785194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catalan Opening |
E1002785
|
entity |
| Predicate | typicalMoveOrder |
P82873
|
FINISHED |
| Object | 1 d4 Nf6 2 c4 e6 3 g3 |
—
|
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 d4 Nf6 2 c4 e6 3 g3 | Statement: [Catalan Opening, typicalMoveOrder, 1 d4 Nf6 2 c4 e6 3 g3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMoveOrder Context triple: [Catalan Opening, typicalMoveOrder, 1 d4 Nf6 2 c4 e6 3 g3]
-
A.
typicalOpeningPattern
Indicates that there is a commonly occurring or characteristic initial configuration, sequence, or arrangement associated with the given context.
-
B.
typicalMovement
Indicates the usual or characteristic way in which an entity moves or is expected to move.
-
C.
typicalOrder
chosen
Indicates the usual or most common sequence or arrangement in which related elements, events, or components occur.
-
D.
commonMove
Indicates that two or more entities share the same movement or relocation event, occurring together or in an identical manner.
-
E.
movementOrderedBy
Indicates that one entity’s movement occurs according to, or is arranged/controlled by, another entity’s ordering or directive.
- 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_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.