Triple
T1184302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alicia Keys |
E25209
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | Alicia |
E25209
|
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: Alicia | Statement: [Alicia Keys, notableWork, Alicia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alicia Context triple: [Alicia Keys, notableWork, Alicia]
-
A.
Alicia
chosen
Alicia is the given name of the American singer, songwriter, and pianist Alicia Keys, known for her soulful R&B music and powerful vocals.
-
B.
Nina
Nina is a Danish fashion model best known for her appearances in the Sports Illustrated Swimsuit Issue and various high-profile advertising campaigns.
-
C.
Rebeca
Rebeca is a feminine given name, commonly used in Spanish- and Portuguese-speaking countries, that is a variant of the name Rebecca.
-
D.
Alix
Alix is the given name of Alix of Hesse and by Rhine, who became Empress Alexandra Feodorovna of Russia as the wife of Tsar Nicholas II.
-
E.
Amalia
Amalia is the Dutch crown princess, heir apparent to the throne of the Kingdom of the Netherlands.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd37b4a88190bb71a2d272c5fd1a |
completed | March 1, 2026, 10:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad08a02ba081908e0036a9d8bfc9f2 |
completed | March 8, 2026, 5:26 a.m. |
Created at: March 1, 2026, 7:45 p.m.