Triple
T20762325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scrabble (in North America) |
E511002
|
entity |
| Predicate | boardDimensions |
P67473
|
FINISHED |
| Object | 15×15 squares |
—
|
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: 15×15 squares | Statement: [Scrabble (in North America), boardDimensions, 15×15 squares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardDimensions Context triple: [Scrabble (in North America), boardDimensions, 15×15 squares]
-
A.
pitchDimensions
Indicates the specific measurements or size parameters that define the extent or layout of a pitch or playing field.
-
B.
typicalDimension
chosen
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
C.
graphicsDimension
Indicates a relationship where an entity has or is associated with a specific graphical size or dimensional properties.
-
D.
flagDimensions
Indicates the specific measurements (such as height, width, or aspect ratio) that define the size of a flag.
-
E.
floorWidth
Indicates the horizontal extent or measurement of how wide a floor is.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2493a188190a336a35ea134e5f7 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:35 p.m.