Triple
T26564413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelliher |
E666336
|
entity |
| Predicate | isAnglicizedFrom |
P143350
|
FINISHED |
| Object | Gaelic surnames |
—
|
LITERAL 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: Gaelic surnames | Statement: [Kelliher, isAnglicizedFrom, Gaelic surnames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAnglicizedFrom Context triple: [Kelliher, isAnglicizedFrom, Gaelic surnames]
-
A.
isOftenAmericanizedFormOf
Indicates that one term is a version of another term that has been adapted into common American usage, typically in spelling, form, or style.
-
B.
hasEnglishName
Indicates that an entity is associated with a name expressed in the English language.
-
C.
isSpokenAs
Indicates that one entity is used as the spoken or verbal form of another entity (e.g., a word, name, or phrase).
-
D.
hasLaterNameInEnglish
Indicates that an entity is known by a different English name at a later time or in a subsequent context.
-
E.
hasNameEtymologyIn
chosen
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
- F. None of above.
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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6149cc0c88190aadaacfa45a2382e |
completed | May 2, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:54 a.m.