Triple
T30337977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chess960 |
E771671
|
entity |
| Predicate | promotionRule |
P43222
|
FINISHED |
| Object | same pawn promotion rules as standard chess |
—
|
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: same pawn promotion rules as standard chess | Statement: [Chess960, promotionRule, same pawn promotion rules as standard chess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionRule Context triple: [Chess960, promotionRule, same pawn promotion rules as standard chess]
-
A.
promotionType
Indicates the specific kind or category of promotion associated with an entity or event.
-
B.
promotionConditions
chosen
Indicates the conditions or criteria that must be met for a promotion to occur between entities.
-
C.
promotionFor
Indicates that one entity serves as a promotional activity, material, or campaign intended to advertise, support, or increase the visibility of another entity.
-
D.
promotionFrom
Indicates that an entity has been elevated in position, rank, or status from a specified prior role or level.
-
E.
promotionBy
Indicates that one entity advances, elevates, or publicizes another entity, typically by increasing its status, visibility, or level.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 29, 2026, 7:54 p.m.