Triple
T3815462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederiksborg Castle |
E84242
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Hillerød |
E95304
|
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: Hillerød | Statement: [Frederiksborg Castle, locatedIn, Hillerød]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hillerød Context triple: [Frederiksborg Castle, locatedIn, Hillerød]
-
A.
Hillerød
chosen
Hillerød is a Danish town on the island of Zealand, known for the historic Frederiksborg Castle and its role as a regional administrative and cultural center.
-
B.
Rødovre
Rødovre is a suburban municipality in the Capital Region of Denmark, located just west of central Copenhagen.
-
C.
Holbæk
Holbæk is a coastal town and municipality in northwestern Zealand, Denmark, known for its harbor on Holbæk Fjord and role as a regional commercial and cultural center.
-
D.
Hellerup
Hellerup is a suburban district just north of central Copenhagen, known for its affluent residential areas, seaside location, and role as a key transport and commercial hub.
-
E.
Næstved
Næstved is a historic market town and commercial center in southern Denmark, located on the island of Zealand.
- 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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee8e05f448190ba15e9ced97bd9fc |
completed | March 9, 2026, 3:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4fb40b0dc8190845bd62774f4a55b |
completed | March 14, 2026, 6:08 a.m. |
Created at: March 9, 2026, 3:17 p.m.