Triple
T12235125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huntly |
E291570
|
entity |
| Predicate | postTown |
P2711
|
FINISHED |
| Object | HUNTLY |
E291570
|
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: HUNTLY | Statement: [Huntly, postTown, HUNTLY]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HUNTLY Context triple: [Huntly, postTown, HUNTLY]
-
A.
Huntly
chosen
Huntly is a historic town in Aberdeenshire, Scotland, long associated with the Gordon family and the Marquess of Huntly.
-
B.
Huntly
Huntly is a small town in New Zealand known for its coal mining history and location on the Waikato River between Hamilton and Auckland.
-
C.
Hamiltoun
Hamiltoun is an archaic or alternative spelling of the Scottish surname and place name Hamilton.
-
D.
Hyndland
Hyndland is an affluent residential district in Glasgow known for its historic tenement buildings, leafy streets, and vibrant local amenities.
-
E.
Braemar
Braemar is a Scottish village in Aberdeenshire renowned for hosting one of the most famous and historic Highland games, traditionally attended by the British royal family.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cb2892c81909a97b3ad6ec2c21b |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60aaf7b348190865a6a1b6de51753 |
completed | May 2, 2026, 2:31 p.m. |
Created at: April 8, 2026, 9:51 p.m.