Triple
T31112849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Bedwyn |
E792998
|
entity |
| Predicate | hasAncientParishStatus |
P183734
|
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, hasAncientParishStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncientParishStatus Context triple: [Great Bedwyn, hasAncientParishStatus, true]
-
A.
hasParishStatusSince
Indicates that an entity has held the status of a parish continuously starting from a specified point in time.
-
B.
hasCivilParishStatus
Indicates that an entity holds the official administrative status or designation of a civil parish.
-
C.
isHistoricParishOf
Indicates that one entity is a historic parish that formerly served, or is recognized as having served, as the parish jurisdiction for another entity.
-
D.
hasParishHistory
Indicates that an entity possesses or is associated with a documented historical record of a parish.
-
E.
hasTraditionalParish
Indicates that an entity is associated with or belongs to a specific traditional parish.
- F. None of above. chosen
Provenance (4 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_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: April 29, 2026, 9:04 p.m.