Triple
T26259589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patrick McDonald |
E656809
|
entity |
| Predicate | hasSurnameLanguageOfOrigin |
P145760
|
FINISHED |
| Object | Scottish Gaelic |
—
|
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: Scottish Gaelic | Statement: [Patrick McDonald, hasSurnameLanguageOfOrigin, Scottish Gaelic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnameLanguageOfOrigin Context triple: [Patrick McDonald, hasSurnameLanguageOfOrigin, Scottish Gaelic]
-
A.
hasSurnameEthymology
chosen
Indicates that an entity’s surname originates from, or is derived based on, a specified source, language, or etymological root.
-
B.
languageOfSurnameVariants
Indicates the language in which particular surname variants are used or originate.
-
C.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
D.
hasPossibleEthnicOriginOfSurname
Indicates that a surname is associated with, or can plausibly originate from, a particular ethnic group or ethnicity.
-
E.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 26, 2026, 9:09 p.m.