Triple
T15437507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aylmerton |
E369803
|
entity |
| Predicate | hasCivilParishName |
P43491
|
FINISHED |
| Object | Aylmerton |
E369803
|
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: Aylmerton | Statement: [Aylmerton, hasCivilParishName, Aylmerton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aylmerton Context triple: [Aylmerton, hasCivilParishName, Aylmerton]
-
A.
Aylmerton
chosen
Aylmerton is a small village in Norfolk, England, situated near the north coast and surrounded by rural countryside.
-
B.
Aigremont
Aigremont is a small French commune located in the Yvelines department in north-central France.
-
C.
Alderton
Alderton is a small rural village and civil parish located in the English county of Suffolk.
-
D.
Westmere
Westmere is a suburban hamlet and census-designated place within the town of Guilderland in Albany County, New York.
-
E.
Westmere
Westmere is Intel's 32 nm microarchitecture, a die-shrink of Nehalem that introduced several new features and performance improvements to the Core processor lineup.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03edca064819081510bf303271062 |
completed | April 16, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff21a7d44481909a26b5cc331a3259 |
completed | May 9, 2026, 11:59 a.m. |
Created at: April 10, 2026, 3:21 a.m.