Triple
T35030597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amelya |
E1010467
|
entity |
| Predicate | hasSpellingVariantRelation |
P457
|
FINISHED |
| Object | Amelia |
—
|
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: Amelia | Statement: [Amelya, hasSpellingVariantRelation, Amelia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpellingVariantRelation Context triple: [Amelya, hasSpellingVariantRelation, Amelia]
-
A.
hasVariantSpelling
chosen
Indicates that one term is an alternative spelling form of another term.
-
B.
hasSpellingVariantFrequency
Indicates a relationship where one spelling variant of a term is associated with how often it occurs relative to other variants.
-
C.
spellingVariantPattern
Indicates a relationship where one form of a word is a systematic spelling variant of another, following a recognizable pattern of orthographic change.
-
D.
hasVariantReadingsWith
Indicates a relationship where two textual items are linked because they exhibit differing or alternative readings of (typically) the same underlying content.
-
E.
hasNameVariantLanguage
Indicates that a name variant is associated with or expressed in a specific language.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:01 p.m.