Triple

T16353426
Position Surface form Disambiguated ID Type / Status
Subject WB Group E397113 entity
Predicate hasSubsidiary P254 FINISHED
Object Radmor E398123 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: Radmor | Statement: [WB Group, hasSubsidiary, Radmor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Radmor
Context triple: [WB Group, hasSubsidiary, Radmor]
  • A. Radmor chosen
    Radmor is a Polish defense company known for developing and manufacturing military communication and radio systems.
  • B. Waldomore
    Waldomore is a historic 19th-century mansion in Clarksburg, West Virginia, known for its Classical Revival architecture and its role as a cultural and archival center for the community.
  • C. Moross
    Moross is a surname most notably associated with American composer Jerome Moross, known for his film and television scores and concert works.
  • D. Blackridge
    Blackridge is a village in West Lothian, Scotland, situated between Bathgate and Armadale with a largely residential and commuter community.
  • E. Dunvant
    Dunvant is a suburban village and community in the City and County of Swansea in south Wales.
  • 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_69d87f26864c819088365ca381a003c2 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2faccab748190b11e0808e422f2ea completed April 18, 2026, 3:30 a.m.
NED1 Entity disambiguation (via context triple) batch_6a002db841dc8190bfe8a0d8fca1b309 completed May 10, 2026, 7:03 a.m.
Created at: April 10, 2026, 5:07 a.m.