Triple
T37075936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patrick Ramsay |
E917708
|
entity |
| Predicate | hasAlternativeSpellingOfSurname |
P96655
|
FINISHED |
| Object | Ramsey |
—
|
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: Ramsey | Statement: [Patrick Ramsay, hasAlternativeSpellingOfSurname, Ramsey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeSpellingOfSurname Context triple: [Patrick Ramsay, hasAlternativeSpellingOfSurname, Ramsey]
-
A.
hasAlternativeFamilyName
chosen
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
-
B.
hasAlternativeToponymy
Indicates that an entity is associated with one or more alternative place names or toponyms used to refer to the same geographic location.
-
C.
languageOfSurnameVariants
Indicates the language in which particular surname variants are used or originate.
-
D.
equivalentSurname
Indicates that two entities share the same surname or are considered to have matching surnames for identification or equivalence purposes.
-
E.
hasAlternativeSpellingOfComposerName
Indicates that one composer's name is an alternative spelling or variant form of another composer's name.
- 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 3, 2026, 4:14 p.m.