Triple
T21498743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian formalism |
E530422
|
entity |
| Predicate | associatedWithOrganization |
P629
|
FINISHED |
| Object | OPOJAZ |
—
|
NE NERFINISHED |
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: OPOJAZ | Statement: [Russian formalism, associatedWithOrganization, OPOJAZ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OPOJAZ Context triple: [Russian formalism, associatedWithOrganization, OPOJAZ]
-
A.
OPOJAZ
chosen
OPOJAZ was a pioneering Russian Formalist literary group in early 20th-century Petrograd that developed influential theories of literary form and technique.
-
B.
OPO
OPO is the IATA airport code for Francisco Sá Carneiro Airport, the main international airport serving Porto, Portugal.
-
C.
OPO
OPO is the vehicle registration code assigned to the Polish city of Opole.
-
D.
OPODIS
OPODIS is an international conference focused on the theory, design, analysis, and implementation of distributed and decentralized systems.
-
E.
OZP
OZP is the IATA airport code for Morón Air Base, a military airfield located near Seville in southern Spain.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea5a1c6481909410a1164d86a344 |
completed | April 23, 2026, 9:46 a.m. |
Created at: April 16, 2026, 6:23 p.m.