Triple
T2453611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austerfield, Yorkshire, England |
E53764
|
entity |
| Predicate | hasDomesdayRecord |
P17484
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Austerfield, Yorkshire, England, hasDomesdayRecord, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomesdayRecord Context triple: [Austerfield, Yorkshire, England, hasDomesdayRecord, yes]
-
A.
isRecordedInDomesdayBook
chosen
Indicates that an entity is documented as existing or being held in the historical Domesday Book survey.
-
B.
domesdayHundred
Indicates that a place or entity is located within, or associated with, a specific administrative hundred as recorded in the Domesday Book.
-
C.
hasHistoricCountyStatusSince
Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
-
D.
hasHistoricCountySeat
Indicates that an administrative region historically had its county government or main county offices located in a particular settlement or city.
-
E.
domesdayBookCompletionYear
Indicates the year in which the Domesday Book was completed.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0aed2688190a18fe66b98d80e0b |
completed | March 7, 2026, 7:15 a.m. |
Created at: March 6, 2026, 9:44 p.m.