Triple
T6754785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North East Fife |
E154426
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Guardbridge |
E317409
|
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: Guardbridge | Statement: [North East Fife, hasTown, Guardbridge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Guardbridge Context triple: [North East Fife, hasTown, Guardbridge]
-
A.
Guardbridge
chosen
Guardbridge is a small Scottish village in Fife, situated near the River Eden and known historically for its paper mill and as a gateway to St Andrews.
-
B.
Almodington
Almodington is a small settlement located on the Manhood Peninsula in West Sussex, England.
-
C.
Geary
Geary is a small crofting settlement on the Waternish peninsula of the Isle of Skye in Scotland.
-
D.
Burgard
Burgard is a German surname borne by individuals such as the computer scientist Wolfram Burgard.
-
E.
Havelock
Havelock is an English surname most notably associated with Sir Henry Havelock, a 19th-century British general known for his role in the Indian Rebellion of 1857.
- 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_69c6880fd5808190be684854081e27dd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1f465388190858207ca4c48f18d |
completed | March 27, 2026, 6:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c71a78feb8819084314c2ae043d289 |
completed | March 28, 2026, 12:02 a.m. |
Created at: March 27, 2026, 2:11 p.m.