Triple
T4667320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Żandarmeria Wojskowa |
E102877
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | ŻW |
E102877
|
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: ŻW | Statement: [Żandarmeria Wojskowa, abbreviation, ŻW]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ŻW Context triple: [Żandarmeria Wojskowa, abbreviation, ŻW]
-
A.
ŻW
chosen
ŻW is the abbreviated name of Poland’s Military Gendarmerie, the armed forces’ military police force responsible for law enforcement and security within the Polish military.
-
B.
ŻZW
ŻZW was a Jewish underground resistance organization in Nazi-occupied Poland, best known for its significant role in the 1943 Warsaw Ghetto Uprising.
-
C.
ZW
ZW is the ISO 3166-1 alpha-2 country code for Zimbabwe, a landlocked country in southern Africa.
-
D.
WZ
WZ is the IATA airline designator assigned to Red Wings Airlines, a Russian passenger carrier.
-
E.
ZWN
ZWN is a former currency code used to denote an early version of the Zimbabwean dollar in international financial and foreign exchange contexts.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd633ec8b08190bf8ffd4c3b946f61 |
completed | March 20, 2026, 3:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be038912488190a109d4ce624b813d |
completed | March 21, 2026, 2:33 a.m. |
Created at: March 20, 2026, 1:15 p.m.