Triple
T36737068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | parish of Stow Bardolph |
E907510
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object |
Barroway Drove
Barroway Drove is a small rural village in Norfolk, England, situated within the parish of Stow Bardolph.
|
E2295619
|
NE 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: Barroway Drove | Statement: [parish of Stow Bardolph, containsSettlement, Barroway Drove]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Barroway Drove Triple: [parish of Stow Bardolph, containsSettlement, Barroway Drove]
Generated description
Barroway Drove is a small rural village in Norfolk, England, situated within the parish of Stow Bardolph.
Provenance (5 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c8fb792881909c52717889255b27 |
completed | May 3, 2026, 10:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a81cb72a0308190a1d4576e267035d8 |
completed | Aug. 16, 2026, 2:38 p.m. |
| NEDg | Description generation | batch_6a81cc0c561881908985a0c22362a210 |
completed | Aug. 16, 2026, 2:41 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a81cc5f482c81909f24d8cedca8635d |
completed | Aug. 16, 2026, 2:42 p.m. |
Created at: May 3, 2026, 4:12 p.m.