Triple
T12726504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarocin |
E304120
|
entity |
| Predicate | hasOfficialName |
P66
|
FINISHED |
| Object | Jarocin |
E304120
|
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: Jarocin | Statement: [Jarocin, hasOfficialName, Jarocin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jarocin Context triple: [Jarocin, hasOfficialName, Jarocin]
-
A.
Jarocin
chosen
Jarocin is a town in west-central Poland known historically for its role in the Greater Poland region and, in modern times, for hosting one of the country’s most famous rock music festivals.
-
B.
Jauer
Jauer is a variety of the Romansh language spoken in parts of the Engadine valley in Switzerland, closely related to the Puter dialect.
-
C.
Jasionka
Jasionka is a village in southeastern Poland best known for hosting the regional Rzeszów–Jasionka Airport.
-
D.
Jachim
Jachim is a given name that serves as a variant form of Joachim, used in various European naming traditions.
-
E.
Grojec
Grojec is a village in southern Poland located in the Lesser Poland region, historically associated with the area around Oświęcim.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96415ebe48190ae935bc3a9b00f65 |
completed | April 10, 2026, 8:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f67c884bd08190bf0022e8303a4987 |
completed | May 2, 2026, 10:36 p.m. |
Created at: April 9, 2026, 5:25 p.m.