Triple
T1694217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryan |
E36618
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Ryen |
E191486
|
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: Ryen | Statement: [Ryan, hasVariant, Ryen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ryen Context triple: [Ryan, hasVariant, Ryen]
-
A.
O'Ryan
O'Ryan is a surname of Irish origin, typically indicating descent from a family or clan associated with the given name Ryan.
-
B.
Yoron
Yoron is a small subtropical island town in Japan’s Kagoshima Prefecture, known for its coral reefs, white-sand beaches, and traditional Ryukyuan-influenced culture.
-
C.
Kadan
Kadan was a Mongol prince and military commander who played a key role in the Mongol invasions of Central and Eastern Europe in the 13th century.
-
D.
Rian
chosen
Rian is a given name, typically used as a variant spelling of Ryan.
-
E.
Treveris
Treveris is the historical city now known as Trier, one of the oldest cities in Germany and a major center of the Roman Empire in the region.
- 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa62b3b8908190afc3f9e4a384684f |
completed | March 6, 2026, 5:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ada0cb18348190baf7a30c231c7349 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 4, 2026, 7:29 p.m.