Triple
T9257215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Dorset |
E222473
|
entity |
| Predicate | isLargelyAgricultural |
P40002
|
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: [North Dorset, isLargelyAgricultural, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLargelyAgricultural Context triple: [North Dorset, isLargelyAgricultural, true]
-
A.
hasAgriculturalCharacter
chosen
Indicates that something possesses qualities, features, or uses typical of agriculture or farming activities.
-
B.
locatedInAgriculturalRegion
Indicates that an entity is situated within a region primarily characterized by agricultural activities or land use.
-
C.
hasAgriculturalProduction
Indicates that an entity engages in or is characterized by the production of agricultural goods such as crops or livestock.
-
D.
isPredominantlyRural
Indicates that a place or region is characterized mainly by rural features, such as low population density and extensive non-urban land use.
-
E.
hasAgriculturalLaborForce
Indicates that an entity possesses a workforce engaged in agricultural activities or farming-related labor.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd06b660448190b6bc04beff0f5512 |
completed | April 1, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:32 p.m.