Triple
T13029950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aylesham |
E326407
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Kent |
E5977
|
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: Kent | Statement: [Aylesham, locatedIn, Kent]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kent Context triple: [Aylesham, locatedIn, Kent]
-
A.
Kent
Kent is a suburban city in King County, Washington, known as a residential and industrial hub within the greater Seattle metropolitan area.
-
B.
Kent
chosen
Kent is a county in southeastern England known for its historic towns, coastal landscapes, and nickname "the Garden of England."
-
C.
Kent
Kent is a brand of filtered cigarettes historically marketed as a "safer" smoking option and produced by the Lorillard Tobacco Company.
-
D.
Kent
Kent is a common English surname famously associated with the adoptive family of Superman in DC Comics, including Jonathan and Martha Kent.
-
E.
Kent
Kent is a common English surname borne by numerous notable individuals across fields such as art, politics, and entertainment.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efd18308190877b3269403b36e2 |
completed | April 10, 2026, 10:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6c12191b08190abf4123995116ebc |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 9, 2026, 8:54 p.m.