Triple
T34153294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treasure Chest Casino |
E876062
|
entity |
| Predicate | typeOfGamingFacility |
P130684
|
FINISHED |
| Object | dockside casino |
—
|
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: dockside casino | Statement: [Treasure Chest Casino, typeOfGamingFacility, dockside casino]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfGamingFacility Context triple: [Treasure Chest Casino, typeOfGamingFacility, dockside casino]
-
A.
typeOfGamblingVenue
chosen
Indicates that one entity is a specific kind or category of gambling venue in relation to another entity.
-
B.
gameZoneType
Indicates the classification or category of a game zone within a game environment (e.g., safe area, combat zone, tutorial area).
-
C.
typeOfGambling
Indicates the specific category or form of gambling activity associated with an entity.
-
D.
typicalGameLocation
Indicates the usual or characteristic place where a game is played or takes place.
-
E.
hasGamingTables
Indicates that an entity provides or contains one or more tables specifically designated for gaming or gambling activities.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0120f070b081909b6d1a3d8ee6b80e |
completed | May 11, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_6a01209da37481909683e38f264b15ef |
completed | May 11, 2026, 12:19 a.m. |
Created at: May 1, 2026, 1:54 a.m.