Triple
T31112847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Bedwyn |
E792998
|
entity |
| Predicate | wasDomesdaySettlement |
P17484
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Great Bedwyn, wasDomesdaySettlement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasDomesdaySettlement Context triple: [Great Bedwyn, wasDomesdaySettlement, true]
-
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.
historicalSettlementType
Indicates the type or category of settlement an entity was historically classified as (e.g., village, town, city) during a past period.
-
D.
wasRomanSettlementName
Indicates that the subject was the name used for a settlement during the Roman period.
-
E.
wasDuchyWithin
Indicates that a political entity held the status of a duchy within the territorial or administrative boundaries of another entity.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:04 p.m.