Triple
T9332197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kennebunkport |
E224549
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Arundel |
E140085
|
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: Arundel | Statement: [Kennebunkport, adjacentTo, Arundel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arundel Context triple: [Kennebunkport, adjacentTo, Arundel]
-
A.
Arundel
chosen
Arundel is a historic market town in southern England, renowned for its medieval castle and cathedral overlooking the River Arun.
-
B.
Thrupp
Thrupp is a small canal-side village in Oxfordshire, England, known for its historic wharf and picturesque setting along the Oxford Canal.
-
C.
Arundell
Arundell is an English noble family name historically associated with prominent aristocratic lineages, particularly in Cornwall and surrounding regions.
-
D.
Dunstable
Dunstable is a historic market town in Bedfordshire, England, known for its location at the crossroads of ancient routes and its proximity to the Chiltern Hills.
-
E.
Willingdon
Willingdon is a village in East Sussex, England, situated near the town of Hailsham.
- 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_69ca8427a0c08190b749831d5ea98f02 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37afceb88190ad7ffbc7b47a1caa |
completed | April 1, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0c806374c819096db10aaa94a6457 |
completed | April 4, 2026, 8:12 a.m. |
Created at: March 30, 2026, 7:39 p.m.