Triple
T22660450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellesborough |
E559645
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | AYLESBURY |
—
|
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: AYLESBURY | Statement: [Ellesborough, hasPostTown, AYLESBURY]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AYLESBURY Context triple: [Ellesborough, hasPostTown, AYLESBURY]
-
A.
Aylesbury
chosen
Aylesbury is a historic market town in southern England that serves as an important commercial and administrative center in Buckinghamshire.
-
B.
Aylesbury Vale
Aylesbury Vale is a largely rural district in Buckinghamshire, England, known for its market town of Aylesbury and its rolling agricultural countryside.
-
C.
Beaconsfield
Beaconsfield is a suburban city on the western part of the Island of Montreal in Quebec, Canada, known for its residential character and waterfront along Lake Saint-Louis.
-
D.
Beaconsfield
Beaconsfield is a small unincorporated rural community located in Ringgold County in southern Iowa, United States.
-
E.
Beaconsfield
Beaconsfield is a historic market town in South East England known for its affluent residential character and well-preserved old town architecture.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765edf88819086c28525e3c73758 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 3:07 p.m.