Triple
T28553278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rakı |
E722942
|
entity |
| Predicate | legalStatusInTurkey |
P44572
|
FINISHED |
| Object | regulated alcoholic beverage |
—
|
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: regulated alcoholic beverage | Statement: [rakı, legalStatusInTurkey, regulated alcoholic beverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInTurkey Context triple: [rakı, legalStatusInTurkey, regulated alcoholic beverage]
-
A.
statusInTurkey
chosen
Indicates the legal, social, or official condition or standing that an entity holds within the context of Turkey.
-
B.
hasLegalStatusInSaudiLaw
Indicates that an entity possesses a specific legal status or recognition under the laws and regulations of Saudi Arabia.
-
C.
legalStatusAccordingToUkraine
Indicates the legal status or classification of an entity as defined specifically by the laws and regulations of Ukraine.
-
D.
legalRationaleClaimedByTurkey
Indicates that a particular legal rationale is asserted or invoked by Turkey as the basis for its position or actions.
-
E.
legalStatusInTaiwan
Indicates the legal status or recognition that an entity has within the jurisdiction of Taiwan.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 28, 2026, 3:44 a.m.