Triple
T750353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Lovelock |
E15432
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object | Abbotsbury |
E93756
|
NE 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: Abbotsbury | Statement: [James Lovelock, residence, Abbotsbury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Abbotsbury Context triple: [James Lovelock, residence, Abbotsbury]
-
A.
Abbotsbury
chosen
Abbotsbury is a historic village on the Jurassic Coast in Dorset, England, known for its scenic coastal setting and ancient abbey ruins.
-
B.
Blandford Forum
Blandford Forum is a historic market town on the River Stour in Dorset, England, noted for its Georgian architecture and rural surroundings.
-
C.
Hawkenbury
Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
-
D.
Upavon
Upavon is a village on Salisbury Plain in Wiltshire, England, notable for its long military association and nearby army and air force facilities.
-
E.
Abinger Hammer
Abinger Hammer is a picturesque village in Surrey, England, known for its historic water-powered clock and scenic setting within the Surrey Hills countryside.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a6304e0c8190827fb57c5cac2da9 |
completed | March 1, 2026, 8:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a67ef89a848190beaf6d1dab0ae331 |
completed | March 3, 2026, 6:26 a.m. |
Created at: March 1, 2026, 7:37 p.m.