Triple
T33607841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ó Sirideáin |
E860907
|
entity |
| Predicate | hasAnglicisationPattern |
P126165
|
FINISHED |
| Object | loss of fada diacritics in Sheridan |
—
|
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: loss of fada diacritics in Sheridan | Statement: [Ó Sirideáin, hasAnglicisationPattern, loss of fada diacritics in Sheridan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnglicisationPattern Context triple: [Ó Sirideáin, hasAnglicisationPattern, loss of fada diacritics in Sheridan]
-
A.
hasBritishAccent
Indicates that the subject speaks with a British accent.
-
B.
hasTraditionalEnglishCharacter
Indicates that something possesses qualities, features, or style typically associated with traditional English culture or heritage.
-
C.
correspondsToEnglishSpelling
chosen
Indicates that one representation, form, or transcription matches or is equivalent to the standard English spelling of the same item.
-
D.
hasEnglishName
Indicates that an entity is associated with a name expressed in the English language.
-
E.
hasStandardizedNameInEnglish
Indicates that an entity is associated with a specific standardized or officially recognized name expressed in English.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 1, 2026, 1:41 a.m.