Triple
T26948195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irish Ó Grádaigh |
E678705
|
entity |
| Predicate | notableAnglicisedBearersSurname |
P87582
|
FINISHED |
| Object | Grady |
—
|
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: Grady | Statement: [Irish Ó Grádaigh, notableAnglicisedBearersSurname, Grady]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAnglicisedBearersSurname Context triple: [Irish Ó Grádaigh, notableAnglicisedBearersSurname, Grady]
-
A.
notableSurnameBranch
Indicates that a particular family branch is distinguished or noteworthy within a broader surname lineage.
-
B.
notableFamilyNameOf
Indicates that a particular family name is notably or prominently associated with a given person or family entity.
-
C.
dynasticSurnameAnglicisedAs
chosen
Indicates that a dynastic surname has an established or commonly used anglicized form derived from its original language.
-
D.
hasNotablePersonWithSurname
Indicates that an entity is associated with at least one notable person who bears a specified surname.
-
E.
hasNotableSurname
Indicates that an entity bears a surname that is recognized as notable, distinguished, or of particular significance.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
Created at: April 27, 2026, 6:23 a.m.