Triple
T3166019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazovia |
E66213
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Warsaw |
E8399
|
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: Warsaw | Statement: [Mazovia, containsCity, Warsaw]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Warsaw Context triple: [Mazovia, containsCity, Warsaw]
-
A.
Warsaw
chosen
Warsaw is the capital and largest city of Poland, known for its resilient history, especially its near-total destruction in World War II and subsequent postwar reconstruction.
-
B.
Lublin
Lublin is a historic city in eastern Poland known as a major cultural, academic, and economic center and for its significant role in Polish political history.
-
C.
Kraków
Kraków is one of Poland’s oldest and most historically significant cities, renowned for its well-preserved medieval core, royal heritage, and cultural institutions.
-
D.
Wilno
Wilno is the historical Polish name for Vilnius, a major cultural and political center of the region that served as an important city in the interwar Second Polish Republic.
-
E.
Łódź
Łódź is one of Poland’s largest cities, historically known as a major industrial and textile manufacturing center.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6424ee48190a29891ffbbc3811d |
completed | March 8, 2026, 4:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4fadc46e8819095ebcb23e1da9947 |
completed | March 14, 2026, 6:06 a.m. |
Created at: March 8, 2026, 3:06 p.m.