Triple
T14880913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingston, East Sussex |
E349996
|
entity |
| Predicate | hasLocalNature |
P87759
|
FINISHED |
| Object | rural settlement |
—
|
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: rural settlement | Statement: [Kingston, East Sussex, hasLocalNature, rural settlement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalNature Context triple: [Kingston, East Sussex, hasLocalNature, rural settlement]
-
A.
hasNature
Indicates that something possesses, exhibits, or is characterized by a particular inherent quality, essence, or fundamental type.
-
B.
isLocalTo
Indicates that one entity is geographically or contextually situated near, or within the same local area or scope as, another entity.
-
C.
isLocalLandmark
Indicates that something is recognized as a notable or significant landmark within a specific local area or community.
-
D.
hasNaturalAreaType
chosen
Indicates that an entity is associated with or classified by a specific type of natural area (e.g., forest, wetland, grassland).
-
E.
hasLimitedNature
Indicates that an entity possesses a restricted, finite, or constrained nature or scope in some respect.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e622388190b2bf91cd10b9821d |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.