Triple
T9735139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZOMO |
E236038
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | ZOMO |
E236038
|
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: ZOMO | Statement: [ZOMO, abbreviation, ZOMO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ZOMO Context triple: [ZOMO, abbreviation, ZOMO]
-
A.
ZOMO
chosen
ZOMO was a militarized riot police force in communist Poland notorious for its brutal suppression of opposition and public protests.
-
B.
ZUM
ZUM is the IATA airport code for Churchill Falls Airport in Newfoundland and Labrador, Canada.
-
C.
ZM
ZM is the stock ticker symbol for Zoom Video Communications, a leading provider of cloud-based video conferencing and online collaboration services.
-
D.
Züm
Züm is Brampton Transit's bus rapid transit service that provides faster, limited-stop connections across key corridors in Brampton and the surrounding region.
-
E.
Somosomo
Somosomo is a coastal village on the Fijian island of Taveuni, known as a traditional center of chiefly authority and local administration.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eee70d48190af5a833d7b33aaa5 |
completed | April 1, 2026, 10:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1afce9834819090949690b4ca8622 |
completed | April 5, 2026, 12:41 a.m. |
Created at: March 30, 2026, 8:22 p.m.