Triple
T9288222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kir |
E223450
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Kir Royal |
E223451
|
NE 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: Kir Royal | Statement: [Kir, hasVariant, Kir Royal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kir Royal Context triple: [Kir, hasVariant, Kir Royal]
-
A.
Kir Royal
chosen
Kir Royal is a classic French champagne cocktail typically made by combining crème de cassis with sparkling wine.
-
B.
Koning
Koning is a Dutch surname and term meaning “king,” commonly used in the Netherlands and Belgium.
-
C.
König
König is a German-language surname borne by numerous individuals, including notable figures in fields such as religion, science, and the arts.
-
D.
Kœnig
Kœnig is a French surname most notably associated with figures such as General Marie-Pierre Kœnig, a prominent military leader during World War II.
-
E.
King-Noel
King-Noel is the hyphenated aristocratic surname borne by William King-Noel, 1st Earl of Lovelace, and his descendants in the British peerage.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0b22753e481908bf19c7da13556d6 |
completed | April 4, 2026, 6:39 a.m. |
Created at: March 30, 2026, 7:35 p.m.