Triple
T7433953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polkemmet Country Park |
E171562
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Polkemmet |
E171562
|
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: Polkemmet | Statement: [Polkemmet Country Park, locatedIn, Polkemmet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Polkemmet Context triple: [Polkemmet Country Park, locatedIn, Polkemmet]
-
A.
Polkemmet
chosen
Polkemmet is a locality in Scotland best known for the former Polkemmet Country Park and its historic estate grounds.
-
B.
Pola
Pola is a historic coastal city on the Istrian Peninsula, known today as Pula in Croatia and famed for its well-preserved Roman amphitheater.
-
C.
Poldi
Poldi is a common German diminutive nickname for the given name Leopold.
-
D.
Poulus
Poulus is a personal name variant derived from the given name Poul.
-
E.
Suliskongen
Suliskongen is a prominent mountain in the Sulitjelma massif of northern Norway, known as one of the major peaks in the Scandinavian border region between Norway and Sweden.
- 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f327480481909c4691fd3333e2ae |
completed | March 27, 2026, 9:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c81f1d8af48190af856b5e2438781d |
completed | March 28, 2026, 6:34 p.m. |
Created at: March 27, 2026, 3:13 p.m.