Triple
T11004820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarrant Gunville House |
E260088
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Tarrant Gunville |
E260088
|
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: Tarrant Gunville | Statement: [Tarrant Gunville House, locatedIn, Tarrant Gunville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tarrant Gunville Context triple: [Tarrant Gunville House, locatedIn, Tarrant Gunville]
-
A.
Tarrant Gunville
chosen
Tarrant Gunville is a small rural village and civil parish in Dorset, England.
-
B.
Glanville
Glanville is a surname most prominently associated with Jerry Glanville, an American football coach and former NFL head coach known for his flamboyant personality and aggressive defensive style.
-
C.
Tarrant Monkton
Tarrant Monkton is a small rural village in Dorset, England, known for its traditional countryside setting and historic parish church.
-
D.
Hawkenbury
Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
-
E.
Tarrant Gunville House
Tarrant Gunville House is a historic country house located in the village of Tarrant Gunville in Dorset, England.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797562de4819097a0e136180d283a |
completed | April 9, 2026, 12:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3a97587708190bf31976a3fbc1015 |
completed | April 18, 2026, 3:55 p.m. |
Created at: April 8, 2026, 9:25 p.m.