Triple
T17097030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andover, Hampshire, England |
E414875
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | ANDOVER |
E182020
|
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: ANDOVER | Statement: [Andover, Hampshire, England, hasPostTown, ANDOVER]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ANDOVER Context triple: [Andover, Hampshire, England, hasPostTown, ANDOVER]
-
A.
Andover, Vermont
Andover, Vermont is a small rural town in southeastern Vermont known for its scenic Green Mountain landscapes and quiet, residential character.
-
B.
Andover
chosen
Andover is a town in Hampshire, England, known in part for its role as a major administrative and logistical center for the British Army.
-
C.
Andover
Andover is a town in northeastern Massachusetts known for its historic New England character, strong public schools, and institutions like Phillips Academy.
-
D.
Andover
Andover is a small rural town in northeastern Connecticut known for its lakes, forests, and residential character.
-
E.
Andover, Connecticut
Andover, Connecticut is a small rural town in northeastern Connecticut known for its quiet residential character and location within Tolland County.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfe92988190aa066745ca9791d5 |
completed | April 18, 2026, 7:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012eedfd7c8190b267dedd403f5f2b |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 5:35 a.m.