Triple
T9288274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kir Royal |
E223451
|
entity |
| Predicate | IBARecognition |
P21446
|
FINISHED |
| Object | not an official IBA cocktail |
—
|
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: not an official IBA cocktail | Statement: [Kir Royal, IBARecognition, not an official IBA cocktail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IBARecognition Context triple: [Kir Royal, IBARecognition, not an official IBA cocktail]
-
A.
recognizesText
Indicates that one entity detects and correctly identifies written or printed text present in or associated with another entity.
-
B.
recognizedByBIE
Indicates that something has been formally acknowledged or certified by the Bureau International des Expositions (BIE).
-
C.
areRecognizedBy
Indicates that one entity acknowledges, identifies, or accepts another entity as valid, known, or legitimate.
-
D.
recognizesDocument
Indicates that one entity acknowledges the validity or authenticity of a document associated with another entity.
-
E.
recognitionStatus
chosen
Indicates the current state or outcome of acknowledging, validating, or officially accepting something or someone.
- 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_69cd0862b34c819097cb7c1777313925 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.