Triple
T25433484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domineering |
E637317
|
entity |
| Predicate | usesBoardType |
P71981
|
FINISHED |
| Object | rectangular grid |
—
|
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: rectangular grid | Statement: [Domineering, usesBoardType, rectangular grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBoardType Context triple: [Domineering, usesBoardType, rectangular grid]
-
A.
hasBoardType
chosen
Indicates that an entity is associated with or uses a specific type or category of board.
-
B.
usesBoardShape
Indicates that one entity employs or is designed to work with a particular board shape as part of its function or configuration.
-
C.
hasBoardComposition
Indicates that an entity has a specific structure or makeup of its governing board, such as the types or proportions of members who serve on it.
-
D.
hasBoards
Indicates that an entity possesses, is equipped with, or includes one or more boards as part of its structure, components, or resources.
-
E.
usesPieceType
Indicates that one entity employs or operates using a specific type or category of piece as part of its function or activity.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6dd99f88190848a5bbee795aa17 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 1:59 p.m.