Triple
T19998245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilovaisk cauldron |
E494251
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Ilovaisk |
—
|
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: Ilovaisk | Statement: [Ilovaisk cauldron, locatedIn, Ilovaisk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ilovaisk Context triple: [Ilovaisk cauldron, locatedIn, Ilovaisk]
-
A.
Ilovaisk
chosen
Ilovaisk is a town in eastern Ukraine’s Donetsk Oblast, known internationally as the site of a major and deadly battle during the war in Donbas.
-
B.
Lubań
Lubań is a historic town in southwestern Poland’s Lower Silesia region, known for its medieval architecture and role as a local transport and trade hub.
-
C.
Lubań
Lubań is a prominent peak in Poland’s Gorce Mountains, known for its scenic views and popular hiking trails.
-
D.
Iwaniska
Iwaniska is a village and the seat of a rural administrative district in south-central Poland’s Świętokrzyskie Voivodeship.
-
E.
Balta
Balta is a city that gained historical significance as a strategic location captured during the Uman–Botoșani offensive in World War II.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe6827481909469129feb9aad91 |
completed | April 20, 2026, 5:18 p.m. |
Created at: April 11, 2026, 3:32 p.m.