Triple
T900240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A25 road |
E19429
|
entity |
| Predicate | regionServed |
P82
|
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: [A25 road, regionServed, Kent]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kent Context triple: [A25 road, regionServed, 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.
Yorkshire
Yorkshire is a historic county in northern England known for its large size, distinctive cultural identity, and significant role in British political, industrial, and literary history.
-
D.
Rutland
Rutland is a small city in central Vermont known historically as a marble quarrying center and as a regional hub for commerce and outdoor recreation.
-
E.
Rutland
Rutland is a small historic county in the East Midlands of England, known for its rural character and Rutland Water reservoir.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad42ecac81909f8bc554d2fe0363 |
completed | March 1, 2026, 9:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7ee02a21c819088e6a137ea306efd |
completed | March 4, 2026, 8:32 a.m. |
Created at: March 1, 2026, 7:39 p.m.