Triple
T22254826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilava fortress |
E550070
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Ilava |
—
|
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: Ilava | Statement: [Ilava fortress, locatedIn, Ilava]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ilava Context triple: [Ilava fortress, locatedIn, Ilava]
-
A.
Ilava
chosen
Ilava is a small town in northwestern Slovakia known for its historic fortress and role as a regional administrative center.
-
B.
Loelva
Loelva is a river flowing through Norway’s scenic Loen valley, known for its glacial origins and striking turquoise waters.
-
C.
Izera
Izera is the Polish name for the Jizera River, a Central European river flowing through the Czech Republic and Poland and forming part of their mutual border.
-
D.
Ilavida
Ilavida is a figure in Hindu mythology known as the wife of the sage Vishrava and mother of the righteous king Kubera.
-
E.
Vydra
Vydra is a river in the Šumava region of the Czech Republic, known for its rocky riverbed, scenic gorges, and role as one of the headwaters of the Otava River.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138c1d70881908df47b0f818c0022 |
completed | April 28, 2026, 10:46 p.m. |
Created at: April 16, 2026, 8:39 p.m.