Triple
T11698090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aidan |
E278047
|
entity |
| Predicate | hasDiminutiveForm |
P456
|
FINISHED |
| Object | Aodhán |
E941601
|
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: Aodhán | Statement: [Aidan, hasDiminutiveForm, Aodhán]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aodhán Context triple: [Aidan, hasDiminutiveForm, Aodhán]
-
A.
Aodhán
chosen
Aodhán is an Irish given name of Gaelic origin, traditionally meaning "little fire" and associated with early Irish saints.
-
B.
Aodh
Aodh is the OpenStack service responsible for alarming and event-based notifications, enabling users to define and trigger actions based on telemetry data.
-
C.
Ruadhán
Ruadhán is an Irish given name of Gaelic origin, traditionally meaning "little red one" and often anglicized as Rowan or Rooney.
-
D.
Ailbhe
Ailbhe is an Irish Gaelic given name, traditionally used for both males and females and often anglicized as Alva.
-
E.
Eoghan
Eoghan is a traditional Irish given name, often anglicized in various forms and historically associated with Gaelic nobility and legendary figures.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47df68c81908a91919a69b4880d |
completed | April 10, 2026, 7:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f417302ffc81908d222c4e01fa3e95 |
completed | May 1, 2026, 3 a.m. |
Created at: April 8, 2026, 9:40 p.m.