Triple
T15437348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Rudham |
E369798
|
entity |
| Predicate | ruralSetting |
P47416
|
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: [East Rudham, ruralSetting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruralSetting Context triple: [East Rudham, ruralSetting, true]
-
A.
semiRuralCharacter
Indicates that a place or area has characteristics intermediate between rural and urban, combining elements of both environments.
-
B.
hasRuralLifestyle
Indicates that an entity lives in or regularly engages in a way of life characteristic of rural areas, such as farming, low population density, and countryside-oriented activities.
-
C.
usesPastoralSetting
Indicates that the action or work is set in an idealized rural or countryside environment characteristic of pastoral themes.
-
D.
isPredominantlyRural
chosen
Indicates that a place or region is characterized mainly by rural features, such as low population density and extensive non-urban 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03edca064819081510bf303271062 |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.