Triple
T30329542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central City, Colorado |
E771437
|
entity |
| Predicate | legalizedActivity |
P58843
|
FINISHED |
| Object | limited-stakes casino gambling |
—
|
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: limited-stakes casino gambling | Statement: [Central City, Colorado, legalizedActivity, limited-stakes casino gambling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalizedActivity Context triple: [Central City, Colorado, legalizedActivity, limited-stakes casino gambling]
-
A.
legalizedIn
chosen
Indicates that an action, substance, or practice is permitted by law within a specified jurisdiction or region.
-
B.
legalizedInstitution
Indicates that an authority has formally granted legal status or approval for an institution to exist or operate.
-
C.
reservedLegalActivity
Indicates that a particular legal action, service, or function is restricted to authorized or qualified parties and may not be performed freely by others.
-
D.
prohibitionActivity
Indicates that a certain activity is forbidden or not allowed to be performed.
-
E.
legalStatusOfItems
Indicates the legal classification or regulatory standing that applies to specified items.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: April 29, 2026, 7:53 p.m.