Triple
T19523280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vidzeme region |
E488456
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Limbaži |
—
|
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: Limbaži | Statement: [Vidzeme region, hasMajorCity, Limbaži]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Limbaži Context triple: [Vidzeme region, hasMajorCity, Limbaži]
-
A.
Limbaži
chosen
Limbaži is a historic town in northern Latvia known for its medieval origins and location within the Vidzeme region.
-
B.
Lauje
Lauje are an indigenous ethnic group of Central Sulawesi, Indonesia, known for their distinct Austronesian language and traditional agrarian lifestyle in the region’s highlands and coastal areas.
-
C.
Ludza
Ludza is one of the principal towns of the Latgale region in eastern Latvia, known for its historic castle ruins and status as one of the country’s oldest settlements.
-
D.
Bavanište
Bavanište is a village in the South Banat District of Serbia, situated within the autonomous province of Vojvodina.
-
E.
Mravaldzali
Mravaldzali is a village located in Georgia’s mountainous Racha region, known for its scenic landscapes and traditional rural character.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e636392444819094f6a2aa1cdf3d42 |
completed | April 20, 2026, 2:20 p.m. |
Created at: April 10, 2026, 1:41 p.m.