Triple
T16546378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Grochów |
E401952
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Grochów |
—
|
NE NERFINISHED |
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: Grochów | Statement: [Battle of Grochów, location, Grochów]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Grochów Context triple: [Battle of Grochów, location, Grochów]
-
A.
Grochów
chosen
Grochów is a historic residential district in the Praga-Południe area of Warsaw, Poland, known for its pre-war architecture and role in the city’s industrial and working-class heritage.
-
B.
Grochowe
Grochowe is a village in southeastern Poland located within the administrative district of Gmina Tuszów Narodowy in the Subcarpathian region.
-
C.
Grodków
Grodków is a small historic town in southwestern Poland known for its medieval origins and traditional Silesian character.
-
D.
Chorobrów
Chorobrów is a village in western Ukraine, historically part of the region of Galicia.
-
E.
Rakowice
Rakowice is a historic district in Kraków, Poland, known for its large military cemetery and proximity to the city center.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fbe3fb48190bad143b50dc73c7e |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:15 a.m.