Triple
T2448628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Zionist Organization |
E53650
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | WZO |
E53650
|
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: WZO | Statement: [World Zionist Organization, abbreviation, WZO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WZO Context triple: [World Zionist Organization, abbreviation, WZO]
-
A.
WZO
chosen
WZO is the commonly used abbreviation for the World Zionist Organization, a global body founded to promote Jewish self-determination and support for the State of Israel.
-
B.
WZ
WZ is the IATA airline designator assigned to Red Wings Airlines, a Russian passenger carrier.
-
C.
ŻW
Ż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.
-
D.
ZWL
ZWL is the currency code for the reintroduced Zimbabwean dollar used in Zimbabwe’s monetary system.
-
E.
ZW
ZW is the ISO 3166-1 alpha-2 country code for Zimbabwe, a landlocked country in southern Africa.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd0dc7ed88190920afd4817c621c9 |
completed | March 7, 2026, 7:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aef0c0069c8190bfb9e71aea4774d3 |
completed | March 9, 2026, 4:09 p.m. |
Created at: March 6, 2026, 9:43 p.m.