Triple

T20583561
Position Surface form Disambiguated ID Type / Status
Subject Sławomir Petelicki E505723 entity
Predicate founderOf P104 FINISHED
Object GROM 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: GROM | Statement: [Sławomir Petelicki, founderOf, GROM]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GROM
Context triple: [Sławomir Petelicki, founderOf, GROM]
  • A. GROM chosen
    GROM is Poland’s elite special operations unit renowned for high-risk counterterrorism, hostage rescue, and unconventional warfare missions.
  • B. Gromovo
    Gromovo is a rural locality in Russia’s Leningrad Oblast, situated within the Priozersky District near the Karelian Isthmus.
  • C. Gromnik
    Gromnik is a village in southern Poland known as a local administrative and cultural center within the Lesser Poland region.
  • D. GOM
    GOM is the National Rail station code for Gomshall railway station in Surrey, England.
  • E. GRO
    GRO is the FAA airport code assigned to Rota International Airport, a public airport serving the island of Rota in the Northern Mariana Islands.
  • 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_69e0b4b9669c8190b8e81fc72817d42c completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a974ee4c819099310b46885a5597 completed April 20, 2026, 10:32 p.m.
Created at: April 16, 2026, 11:40 a.m.