Triple
T13344738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conchobhar |
E317919
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Irish personal name |
C2830
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ancient Irish personal name Context triple: [Conchobhar, instanceOf, ancient Irish personal name]
-
A.
Irish-language name
An Irish-language name is a personal or place name originating in the Irish (Gaeilge) language, often reflecting traditional Gaelic phonology, spelling, and cultural heritage.
-
B.
Gaelic name
A Gaelic name is a personal or place name originating from the Gaelic languages (Irish, Scottish, or Manx), typically reflecting Celtic linguistic forms, cultural heritage, and traditional naming patterns.
-
C.
Irish given name
chosen
An Irish given name is a personal first name originating from Ireland, often derived from the Irish language and reflecting the country’s cultural, historical, or religious traditions.
-
D.
Celtic given name
A Celtic given name is a personal first name originating from the Celtic languages and cultures, often reflecting nature, mythology, or historical figures from Celtic traditions.
-
E.
hypothesized Old English personal name
A hypothesized Old English personal name is a reconstructed or inferred individual name from the Old English period that lacks direct attestation in surviving historical records but is proposed based on linguistic and onomastic evidence.
- F. None of above.
Provenance (1 batch)
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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:31 p.m.