Triple
T5755967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benenden School |
E126966
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Benenden |
E126966
|
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: Benenden | Statement: [Benenden School, locatedIn, Benenden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Benenden Context triple: [Benenden School, locatedIn, Benenden]
-
A.
Benenden
chosen
Benenden is a rural village in Kent, England, known for its historic parish church, traditional village green, and the independent girls’ school Benenden School.
-
B.
Tesseney
Tesseney is a town in western Eritrea near the Sudanese border, serving as a local commercial and agricultural center in the Gash-Barka region.
-
C.
Banwen
Banwen is a small village in South Wales, known historically for its coal mining heritage and location near the upper Dulais Valley.
-
D.
Bamble
Bamble is a coastal municipality in Vestfold og Telemark county in southeastern Norway.
-
E.
Bendale
Bendale is a residential neighbourhood located in the Scarborough district of Toronto, Ontario, Canada.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02906848c8190bf7b0d62f57c27fa |
completed | March 22, 2026, 5:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c07e47c1788190b5883df385475237 |
completed | March 22, 2026, 11:41 p.m. |
Created at: March 22, 2026, 3:49 p.m.