Triple
T12216595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plzeň-South District |
E291101
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Losiná |
E961510
|
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: Losiná | Statement: [Plzeň-South District, containsSettlement, Losiná]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Losiná Context triple: [Plzeň-South District, containsSettlement, Losiná]
-
A.
Losiná
chosen
Losiná is a small municipality and village located in the Plzeň Region of the Czech Republic.
-
B.
Lanuza
Lanuza is a coastal municipality in the Philippine province of Surigao del Sur known for its surfing spots and natural scenery.
-
C.
Loiceño
Loiceño is the Spanish demonym for a person from the municipality of Loíza in Puerto Rico.
-
D.
Lopevi
Lopevi is an Oceanic language of Vanuatu, traditionally spoken on Lopevi Island in the central part of the archipelago.
-
E.
Libo
Libo is an ancient Roman cognomen associated with members of the patrician Julii family.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91c9419d48190b0037fe8edc681c4 |
completed | April 10, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60aa31f548190bd4f8cfe3c55614b |
completed | May 2, 2026, 2:30 p.m. |
Created at: April 8, 2026, 9:51 p.m.