Triple
T9286211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadwood, South Dakota |
E223399
|
entity |
| Predicate | legalizedGamblingIn |
P58843
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Deadwood, South Dakota, legalizedGamblingIn, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalizedGamblingIn Context triple: [Deadwood, South Dakota, legalizedGamblingIn, 1989]
-
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.
typeOfGambling
Indicates the specific category or form of gambling activity associated with an entity.
-
D.
legalAbolition
Indicates that a law, practice, or legal status has been formally ended or revoked through an official legal process.
-
E.
recognizedBySomeStatesAs
Indicates that an entity is officially acknowledged or accepted in a particular status or capacity by at least some, but not necessarily all, states.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0821b1108190b16e9570b09a14de |
completed | April 1, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.