Triple
T20761964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monopoly |
E510996
|
entity |
| Predicate | boardLayout |
P82853
|
FINISHED |
| Object | square track of 40 spaces |
—
|
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 track of 40 spaces | Statement: [Monopoly, boardLayout, square track of 40 spaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardLayout Context triple: [Monopoly, boardLayout, square track of 40 spaces]
-
A.
boardProperties
Indicates a relationship where specific attributes or characteristics are assigned to or associated with a board.
-
B.
board
Indicates that an agent gets onto or into a vehicle, vessel, or craft in order to travel or be transported.
-
C.
deckLocation
Indicates the specific deck or level on which an entity is located within a multi-deck structure or vehicle.
-
D.
stationLayout
Indicates the spatial arrangement and structural organization of elements within a station.
-
E.
usesBoardShape
chosen
Indicates that one entity employs or is designed to work with a particular board shape as part of its function or configuration.
- 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.