Triple
T27750343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Backgammon |
E702097
|
entity |
| Predicate | hasOpeningSetup |
P174260
|
FINISHED |
| Object | fixed |
—
|
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: fixed | Statement: [Backgammon, hasOpeningSetup, fixed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningSetup Context triple: [Backgammon, hasOpeningSetup, fixed]
-
A.
hasOpeningSetting
Indicates that one entity (typically a narrative work) has its initial scene or setting located in the other entity.
-
B.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
C.
hasOpeningMovement
Indicates that a work, performance, or sequence includes a distinct initial movement or section that begins the overall piece.
-
D.
hasOpeningCondition
Indicates that a relationship or action is subject to a specific initial condition that must be met before it can begin or take effect.
-
E.
hasOpeningType
Indicates that one entity has, features, or is characterized by a particular type or kind of opening.
- F. None of above. chosen
Provenance (4 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69f6bbf5a8288190ae170bcbe8ab65cf |
completed | May 3, 2026, 3:07 a.m. |
Created at: April 27, 2026, 4:19 p.m.