Triple
T13468600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radom Voivodeship |
E311569
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Grójec |
E1133884
|
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: Grójec | Statement: [Radom Voivodeship, containsCity, Grójec]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Grójec Context triple: [Radom Voivodeship, containsCity, Grójec]
-
A.
Grójec
chosen
Grójec is a town in east-central Poland known for its apple-growing region and proximity to Warsaw.
-
B.
Łeba
Łeba is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
-
C.
Olsztynek
Olsztynek is a small historic town in northern Poland known for its open-air ethnographic museum and location within the picturesque Warmian-Masurian lake district.
-
D.
Grajewo
Grajewo is a town in northeastern Poland known as a local administrative and industrial center near the border with the Warmian-Masurian region.
-
E.
Żoliborz
Żoliborz is a residential district in northern Warsaw, Poland, known for its interwar modernist architecture, green spaces, and quiet, upscale character.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf21e46081908a00c9acf54f270f |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffdbb445a48190ba3dafb1f076ac83 |
completed | May 10, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:42 p.m.