Triple
T20762324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scrabble (in North America) |
E511002
|
entity |
| Predicate | blankTilePointValue |
P141420
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Scrabble (in North America), blankTilePointValue, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blankTilePointValue Context triple: [Scrabble (in North America), blankTilePointValue, 0]
-
A.
MonopolyBoardPositionType
Indicates the specific type or category of a position on a Monopoly board, such as property, utility, railroad, tax, or special spaces like Chance or Jail.
-
B.
ballPlacement
Indicates the spatial positioning or arrangement of a ball relative to a reference point, object, or area.
-
C.
tileCount
Indicates the number of tiles associated with or contained by a given entity or area.
-
D.
whiteDiscPosition
Indicates the spatial location or coordinates where the white disc is currently situated.
-
E.
MonopolyPositionRelativeToGo
Indicates that an entity’s position or status is defined or evaluated in relation to the reference point “Go” within a Monopoly-like positional framework.
- 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_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. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:35 p.m.