Triple
T30139484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watford Rural District Council |
E766087
|
entity |
| Predicate | administeredAreaNear |
P34698
|
FINISHED |
| Object | Watford |
—
|
NE NERFINISHED |
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: Watford | Statement: [Watford Rural District Council, administeredAreaNear, Watford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administeredAreaNear Context triple: [Watford Rural District Council, administeredAreaNear, Watford]
-
A.
hasNearbyGeographicalArea
Indicates that one geographical area is located in close spatial proximity to another geographical area.
-
B.
locatedNearPass
Indicates that one entity is situated close to a mountain pass or similar passageway.
-
C.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
D.
administrativeCentreNearby
chosen
Indicates that an administrative centre is located close to the referenced entity in geographic or spatial terms.
-
E.
nearbyRegionCharacterizedBy
Indicates that a region located nearby another entity is defined or distinguished by a particular characteristic, feature, or condition.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 29, 2026, 7:17 p.m.