Triple
T16668416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Askeran Fortress |
E405042
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Askeran |
E405042
|
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: Askeran | Statement: [Askeran Fortress, locatedIn, Askeran]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Askeran Context triple: [Askeran Fortress, locatedIn, Askeran]
-
A.
Askeran
chosen
Askeran is a town in the disputed Nagorno-Karabakh region of the South Caucasus, historically known for its strategic location and fortress.
-
B.
Asker
Asker is a municipality in Viken county, Norway, known for its coastal location near Oslo and its mix of residential areas, cultural sites, and natural landscapes.
-
C.
Aske
Aske is a surname of Scandinavian origin borne by various individuals, including those with the given name Ellen.
-
D.
Asker, Norway
Asker, Norway is a suburban municipality southwest of Oslo known for its affluent residential areas, coastal landscapes along the Oslofjord, and role as home to members of the Norwegian royal family.
-
E.
Lilleaker
Lilleaker is a residential neighborhood in western Oslo, Norway, known for its mix of housing, green areas, and proximity to the Lysaker River.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9e9a208190afab499897ce4361 |
completed | April 18, 2026, 12:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a008a34852c81908c00ff8e36923cee |
completed | May 10, 2026, 1:37 p.m. |
Created at: April 10, 2026, 5:18 a.m.