Triple
T19951014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aske |
E479553
|
entity |
| Predicate | hasVariantForm |
P457
|
FINISHED |
| Object | Askesen |
—
|
NE NERFINISHED |
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: Askesen | Statement: [Aske, hasVariantForm, Askesen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Askesen Context triple: [Aske, hasVariantForm, Askesen]
-
A.
Asen
Asen was a medieval Bulgarian noble and co-leader, with his brother Peter, of the uprising that restored the Second Bulgarian Empire in the late 12th century.
-
B.
Akesines
Akesines is an ancient name, often used in classical sources, for the river now known as the Chenab in the northwestern Indian subcontinent.
-
C.
Aske
chosen
Aske is a surname of Scandinavian origin borne by various individuals, including those with the given name Ellen.
-
D.
Aspelare
Aspelare is a village and municipal district of the city of Ninove in the Flemish province of East Flanders, Belgium.
-
E.
Andselv
Andselv is a small Norwegian village located in the Troms region, known for its position along the Andselva river and proximity to Bardufoss.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6b694c819080daea9422bcdd38 |
completed | April 20, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:54 p.m.