Triple
T33058519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Frycheiniog |
E845908
|
entity |
| Predicate | historicNamePreservedIn |
P145623
|
FINISHED |
| Object | modern county of Powys |
—
|
LITERAL FINISHED |
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: modern county of Powys | Statement: [Sir Frycheiniog, historicNamePreservedIn, modern county of Powys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicNamePreservedIn Context triple: [Sir Frycheiniog, historicNamePreservedIn, modern county of Powys]
-
A.
historicalNameOfSite
Indicates that one name is a former or past name historically used for a given site or location.
-
B.
historicalNameGivenBy
Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
-
C.
historicallyNamedAfter
Indicates that one entity received its name from another entity at some point in the past.
-
D.
historicalNameUsedIn
chosen
Indicates that a historical or former name was used to refer to a particular entity in some context.
-
E.
historicalNameUntil
Indicates that an entity bore a particular historical name up to a specified point in time, after which that name was no longer used.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffcb5536d88190bfc2e00b854cacfb |
completed | May 10, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69ffc900c2a081909dea04aa60566923 |
completed | May 9, 2026, 11:53 p.m. |
Created at: May 1, 2026, 1:25 a.m.