Triple
T31843421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aberystwith and Welsh Coast Railway |
E812868
|
entity |
| Predicate | modernSpellingOfTown |
P97846
|
FINISHED |
| Object | Aberystwyth |
—
|
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: Aberystwyth | Statement: [Aberystwith and Welsh Coast Railway, modernSpellingOfTown, Aberystwyth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernSpellingOfTown Context triple: [Aberystwith and Welsh Coast Railway, modernSpellingOfTown, Aberystwyth]
-
A.
currentOfficialSpelling
Indicates the officially recognized and currently valid spelling form of a given name or term.
-
B.
spellingReplacedBy
Indicates that one spelling of a term has been superseded or substituted by another spelling.
-
C.
originalSpelling
Indicates that one entity provides the initial or historically first-used spelling form of another entity’s name or term.
-
D.
modernNameForm
chosen
Indicates that one entity is the contemporary or currently used name form corresponding to another entity’s name.
-
E.
scripturalSpelling
Indicates that one form of a word or name is the spelling used in a particular scriptural or sacred text.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 30, 2026, 11:49 p.m.