Triple
T28524788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington State Liquor and Cannabis Board |
E721875
|
entity |
| Predicate | changedNameToInclude |
P26624
|
FINISHED |
| Object | cannabis |
—
|
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: cannabis | Statement: [Washington State Liquor and Cannabis Board, changedNameToInclude, cannabis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedNameToInclude Context triple: [Washington State Liquor and Cannabis Board, changedNameToInclude, cannabis]
-
A.
renamedToInclude
chosen
Indicates that an entity has been renamed so that its new name explicitly includes another specified element (such as a term, identifier, or component).
-
B.
changesNameTo
Indicates that an entity alters its current name and adopts a new specified name.
-
C.
changedNameIn
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
-
D.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
-
E.
changedNameBy
Indicates that one entity altered or updated the name of another entity.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fa5154c8190b1627befc676b1e8 |
completed | May 2, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:23 a.m.