Triple
T26423357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglian settlement of Eoforwic |
E664300
|
entity |
| Predicate | countyInPresentDay |
P138392
|
FINISHED |
| Object | North Yorkshire |
—
|
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: North Yorkshire | Statement: [Anglian settlement of Eoforwic, countyInPresentDay, North Yorkshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countyInPresentDay Context triple: [Anglian settlement of Eoforwic, countyInPresentDay, North Yorkshire]
-
A.
isNamedCountyOf
Indicates that a county bears a specific official name within a given jurisdiction or context.
-
B.
hasFormerCounty
Indicates that an entity was previously part of, or administered by, a particular county in the past but no longer is.
-
C.
hasCurrentCounty
chosen
Indicates that an entity is currently located within, administered by, or associated with a specific county.
-
D.
establishedAsCountyInCurrentForm
Indicates that an administrative region became a county in its present organizational or territorial form on a specific date or during a specific period.
-
E.
inCountySeatRegionOf
Indicates that a county seat is located within and serves as the administrative center for a specified region.
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 26, 2026, 11:44 p.m.