Triple
T10707012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pori |
E252433
|
entity |
| Predicate | hasNeighbouringMunicipality |
P224
|
FINISHED |
| Object | Luvia |
E777397
|
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: Luvia | Statement: [Pori, hasNeighbouringMunicipality, Luvia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Luvia Context triple: [Pori, hasNeighbouringMunicipality, Luvia]
-
A.
Luvia
chosen
Luvia is a coastal municipality in western Finland, located in the Satakunta region along the Gulf of Bothnia.
-
B.
Renaelva
Renaelva is a river in eastern Norway that flows through Hedmark county before joining the larger Glomma river.
-
C.
Lizella
Lizella is an unincorporated community in central Georgia, United States, located near the city of Macon.
-
D.
Nerissa
Nerissa is a witty and loyal lady-in-waiting to Portia in Shakespeare’s play "The Merchant of Venice," known for her intelligence, humor, and role in the play’s romantic subplots.
-
E.
Adalinda
Adalinda was a medieval noblewoman known primarily as the wife of William I, Duke of Aquitaine.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fddfbed48190810bb3faee473fde |
completed | April 9, 2026, 1:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d9990760b48190a05753974cdf556c |
completed | April 11, 2026, 12:42 a.m. |
Created at: April 8, 2026, 9:12 p.m.