Triple
T40331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Martin’s Church, Bladon, Oxfordshire |
E797
|
entity |
| Predicate | servesSettlement |
P2741
|
FINISHED |
| Object | village of Bladon |
—
|
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: village of Bladon | Statement: [St Martin’s Church, Bladon, Oxfordshire, servesSettlement, village of Bladon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesSettlement Context triple: [St Martin’s Church, Bladon, Oxfordshire, servesSettlement, village of Bladon]
-
A.
settlementType
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
-
B.
settled
Indicates that an entity established residence or a stable presence in a place, typically after moving from elsewhere.
-
C.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
-
D.
servesBranch
Indicates that one entity provides services or support to a particular branch or subdivision of an organization.
-
E.
servesMode
Indicates that one entity provides or operates in a particular manner, method, or mode in relation to another entity or context.
- 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24b80f4a8819090d2bffe29824b90 |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ab74c548190a54872e15c8394c3 |
completed | Feb. 28, 2026, 1:53 a.m. |
| PDg | Predicate description generation | batch_69a24b7fd2c08190a0057fe7aec6a1ee |
completed | Feb. 28, 2026, 1:57 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.