Triple
T11921064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid Worcestershire |
E283654
|
entity |
| Predicate | containsAgriculturalLand |
P24310
|
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: [Mid Worcestershire, containsAgriculturalLand, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsAgriculturalLand Context triple: [Mid Worcestershire, containsAgriculturalLand, yes]
-
A.
hasAgriculturalCharacter
Indicates that something possesses qualities, features, or uses typical of agriculture or farming activities.
-
B.
hasAgriculturalProduction
Indicates that an entity engages in or is characterized by the production of agricultural goods such as crops or livestock.
-
C.
hasAgriculturalCommunities
Indicates that certain groups or settlements engage in organized farming and related agricultural activities within a given area or context.
-
D.
locatedInAgriculturalRegion
chosen
Indicates that an entity is situated within a region primarily characterized by agricultural activities or land use.
-
E.
hasRuralArea
Indicates that an entity includes, is associated with, or contains a countryside or sparsely populated geographic 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8e1b08481909ed291667035f330 |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.