Triple
T8482411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go |
E200551
|
entity |
| Predicate | usesBoardShape |
P82853
|
FINISHED |
| Object | square 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: square grid | Statement: [Go, usesBoardShape, square grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBoardShape Context triple: [Go, usesBoardShape, square grid]
-
A.
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.
-
B.
hasBoardType
Indicates that an entity is associated with or uses a specific type or category of board.
-
C.
hasBoardSize
Indicates that an entity is associated with a board whose dimensions or overall size are specified.
-
D.
board
Indicates that an agent gets onto or into a vehicle, vessel, or craft in order to travel or be transported.
-
E.
usesBallShape
Indicates that one entity employs or incorporates a ball-like (spherical) shape in its form, design, or operation.
- 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53638c48190b742fc51d1b4442a |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:12 p.m.