Triple
T7793217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isleworth |
E180231
|
entity |
| Predicate | hasHistoricalName |
P2834
|
FINISHED |
| Object | Gistelworde |
E180231
|
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: Gistelworde | Statement: [Isleworth, hasHistoricalName, Gistelworde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gistelworde Context triple: [Isleworth, hasHistoricalName, Gistelworde]
-
A.
Gistelworde
chosen
Gistelworde is an old historical name once used for the town of Isleworth in Middlesex, England.
-
B.
Horebeke
Horebeke is a small rural municipality in the Flemish Ardennes region of East Flanders, Belgium.
-
C.
Lembeek
Lembeek is a village in the Belgian municipality of Halle, located along the Senne River in the province of Flemish Brabant.
-
D.
Biezelinge
Biezelinge is a small village in the Dutch province of Zeeland, known as the birthplace of former Prime Minister Jan Peter Balkenende.
-
E.
Woubrugge
Woubrugge is a village in the Dutch province of South Holland, known for its location along waterways and its traditional rural character.
- 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_69ca827d22208190b4dc5aa680edcf5d |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cae939c7388190b36d3e746be27a4d |
completed | March 30, 2026, 9:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb13dbe1f88190bde2c5c76dcfeb8f |
completed | March 31, 2026, 12:22 a.m. |
Created at: March 30, 2026, 4:31 p.m.