Triple
T31142887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ossory kingship line of Mac Giolla Phádraig |
E793837
|
entity |
| Predicate | hasAnglicisedSurnameForm |
P87582
|
FINISHED |
| Object | Fitzpatrick |
—
|
NE NERFINISHED |
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: Fitzpatrick | Statement: [Ossory kingship line of Mac Giolla Phádraig, hasAnglicisedSurnameForm, Fitzpatrick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnglicisedSurnameForm Context triple: [Ossory kingship line of Mac Giolla Phádraig, hasAnglicisedSurnameForm, Fitzpatrick]
-
A.
isEquivalentSurnameInEnglish
Indicates that two surnames are considered equivalent when rendered or transliterated into English.
-
B.
dynasticSurnameAnglicisedAs
chosen
Indicates that a dynastic surname has an established or commonly used anglicized form derived from its original language.
-
C.
hasLaterNameInEnglish
Indicates that an entity is known by a different English name at a later time or in a subsequent context.
-
D.
hasEnglishName
Indicates that an entity is associated with a name expressed in the English language.
-
E.
languageOfSurnameVariants
Indicates the language in which particular surname variants are used or originate.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 29, 2026, 9:06 p.m.