Triple
T7263141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warsaw metropolitan area |
E159704
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Piaseczno |
E879624
|
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: Piaseczno | Statement: [Warsaw metropolitan area, containsCity, Piaseczno]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Piaseczno Context triple: [Warsaw metropolitan area, containsCity, Piaseczno]
-
A.
Parczew
Parczew is a small town in eastern Poland known for its historical roots and location within the Lublin region.
-
B.
Siedlce
Siedlce is a city in eastern Poland known as a local economic, cultural, and transportation hub.
-
C.
Pruszków
chosen
Pruszków is a town in east-central Poland that functions as a suburban satellite of Warsaw within its metropolitan area.
-
D.
Ostrołęka
Ostrołęka is a town in east-central Poland known for its historical role in the Napoleonic Wars and as a local industrial and administrative center.
-
E.
Wołosate
Wołosate is a small village in southeastern Poland’s Bieszczady Mountains, known as a remote hiking base and the terminus of the Main Beskid Trail.
- 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eac9fab88190881ab9e1cd94cdc1 |
completed | March 27, 2026, 8:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d99859b5cc81908475fde408802607 |
completed | April 11, 2026, 12:39 a.m. |
Created at: March 27, 2026, 2:57 p.m.