Triple
T15205908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sutton Courtenay |
E363387
|
entity |
| Predicate | hasDomesdayEntry |
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: [Sutton Courtenay, hasDomesdayEntry, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomesdayEntry Context triple: [Sutton Courtenay, hasDomesdayEntry, 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.
wasDuchyWithin
Indicates that a political entity held the status of a duchy within the territorial or administrative boundaries of another entity.
-
D.
hasHistoricCountyStatusSince
Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
-
E.
hasHistoricCountyCore
Indicates that an entity is fundamentally based in, derived from, or primarily associated with a particular historic county as its core area.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b7964c8190bc8dc3444b94f15e |
completed | April 15, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69deb97ee9d881908711dbe12a55283c |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:11 a.m.