Triple
T35571507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chess |
E1027950
|
entity |
| Predicate | hasPopularOpeningPhase |
P75603
|
FINISHED |
| Object | opening |
—
|
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: opening | Statement: [Chess, hasPopularOpeningPhase, opening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopularOpeningPhase Context triple: [Chess, hasPopularOpeningPhase, opening]
-
A.
hasFamousOpening
Indicates that something (such as a work, speech, or performance) is characterized by a widely recognized and notable beginning section.
-
B.
hasCentralOpeningType
Indicates that an entity possesses a central opening characterized by a specific type or form.
-
C.
hasPhaseOfPlay
chosen
Indicates a relationship where a broader game or activity includes or is associated with a specific phase or segment of play.
-
D.
usesOpeningBooks
Indicates that one entity employs predefined opening sequences or reference materials as a guide when initiating an action or process involving another entity.
-
E.
hasOpeningSetup
Indicates that an entity includes or is associated with an initial configuration, arrangement, or setup phase that establishes starting conditions for something.
- 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_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
Created at: May 3, 2026, 4:04 p.m.