Triple
T12354283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pernik Province |
E294567
|
entity |
| Predicate | hasIndustrialCenter |
P3436
|
FINISHED |
| Object | Pernik |
E294570
|
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: Pernik | Statement: [Pernik Province, hasIndustrialCenter, Pernik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pernik Context triple: [Pernik Province, hasIndustrialCenter, Pernik]
-
A.
Pernik
chosen
Pernik is an industrial city in western Bulgaria, historically known for its coal mining and heavy industry, located southwest of Sofia.
-
B.
Pernå
Pernå is a historic former municipality in southern Finland, known as the birthplace of Mikael Agricola, the father of written Finnish.
-
C.
Pernaja
Pernaja is a former municipality and coastal village in southern Finland, now part of the town of Loviisa.
-
D.
Pirk
Pirk is a small municipality in the Upper Palatinate region of Bavaria, Germany.
-
E.
Poriem
Poriem is a legislative assembly constituency in the Indian state of Goa, represented in the Goa Legislative Assembly.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f8bc60c8190b0ceb84093e70db4 |
completed | April 10, 2026, 6:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f63ef437d08190b09132fa090504a5 |
completed | May 2, 2026, 6:14 p.m. |
Created at: April 8, 2026, 9:54 p.m.