Triple
T16284258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lashana Lynch |
E395347
|
entity |
| Predicate | characterPortrayed |
P1507
|
FINISHED |
| Object | Nomi |
E387480
|
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: Nomi | Statement: [Lashana Lynch, characterPortrayed, Nomi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nomi Context triple: [Lashana Lynch, characterPortrayed, Nomi]
-
A.
Nomi
chosen
Nomi is the new 00-agent who succeeds James Bond in the 2021 James Bond film "No Time to Die."
-
B.
Nōmi
Nōmi was a former town in Hiroshima Prefecture, Japan, that later became part of the city of Etajima through a municipal merger.
-
C.
Namin
Namin is a city in Iran known for its location in the mountainous, historically rich Ardabil region in the northwest of the country.
-
D.
Némi
Némi is an Oceanic language spoken by a small indigenous community in New Caledonia.
-
E.
Nomi Sunrider
Nomi Sunrider is a prominent Jedi Knight from the Star Wars Expanded Universe, known for her powerful connection to the Force and key role in the events of the Old Republic era.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24912c5808190a0d9c9f491315068 |
completed | April 17, 2026, 2:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0017c8f51c8190b73cdf2834eda57f |
completed | May 10, 2026, 5:29 a.m. |
Created at: April 10, 2026, 5:05 a.m.