Triple
T9929811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O'Ryan |
E192615
|
entity |
| Predicate | hasEtymologicalElement |
P5801
|
FINISHED |
| Object | Ryan (personal name) |
E36618
|
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: Ryan (personal name) | Statement: [O'Ryan, hasEtymologicalElement, Ryan (personal name)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ryan (personal name) Context triple: [O'Ryan, hasEtymologicalElement, Ryan (personal name)]
-
A.
Ryan (surname)
Ryan is a common Irish surname, anglicized from the Gaelic Ó Riain, and widely borne in Ireland and among the Irish diaspora.
-
B.
Ryan
chosen
Ryan is a masculine given name of Irish origin that is widely used in English-speaking countries.
-
C.
Ryann
Ryann is a given name, typically used as a modern variant of the name Ryan.
-
D.
Ryans
Ryans is the surname of DeMeco Ryans, a former NFL linebacker and current head coach of the Houston Texans.
-
E.
O'Ryan
O'Ryan is a surname of Irish origin, typically indicating descent from a family or clan associated with the given name Ryan.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b215c481909e0bca43f158bd82 |
completed | April 2, 2026, 12:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d20e258e888190ae4e2abac80e3399 |
completed | April 5, 2026, 7:24 a.m. |
Created at: March 30, 2026, 8:43 p.m.