Triple
T697067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montgomeryshire |
E13915
|
entity |
| Predicate | historicCountyCode |
P10086
|
FINISHED |
| Object | MGY |
—
|
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: MGY | Statement: [Montgomeryshire, historicCountyCode, MGY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicCountyCode Context triple: [Montgomeryshire, historicCountyCode, MGY]
-
A.
historicalCounty
Indicates that an entity was located within or associated with a county as it existed in the past, even if that county’s boundaries or administrative status have since changed.
-
B.
hasHistoricCountySeat
Indicates that an administrative region historically had its county government or main county offices located in a particular settlement or city.
-
C.
ceremonialCounty
Indicates that one entity is the ceremonial (non-administrative, often traditional or representational) county associated with the other entity.
-
D.
hasCountyCode
chosen
Indicates that an entity is associated with a specific county identified by a standardized county code.
-
E.
shireCounty
Indicates the county-level administrative area (shire county) within which a given place or entity is located or governed.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c8055881909565ebde2be8fd7a |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d2586b081908e052cc5ba1d2685 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.