Triple
T35571503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chess |
E1027950
|
entity |
| Predicate | hasTimeControlVariant |
P82857
|
FINISHED |
| Object | classical 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: classical chess | Statement: [Chess, hasTimeControlVariant, classical chess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeControlVariant Context triple: [Chess, hasTimeControlVariant, classical chess]
-
A.
usesTimeControlDefinition
Indicates that an entity applies or follows a specific time control definition when governing the timing or duration of an activity or process.
-
B.
typicalTimeControl
chosen
Indicates the usual or standard time control under which an activity, event, or process is typically conducted.
-
C.
timeToControl
Indicates the amount of time required for an entity to gain or establish control over another entity, process, or situation.
-
D.
timeUnderControlOfUnitedStates
Indicates that, during a specified time period, the referenced entity was under the political or administrative control of the United States.
-
E.
hasCentralOpeningType
Indicates that an entity possesses a central opening characterized by a specific type or form.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:04 p.m.