Triple

T29777949
Position Surface form Disambiguated ID Type / Status
Subject Mark Janus E755432 entity
Predicate religionOrPoliticalView P195677 FINISHED
Object supports right‑to‑work principles LITERAL 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: supports right‑to‑work principles | Statement: [Mark Janus, religionOrPoliticalView, supports right‑to‑work principles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: religionOrPoliticalView
Context triple: [Mark Janus, religionOrPoliticalView, supports right‑to‑work principles]
  • A. religiousAttitude
    Indicates an entity’s stance, disposition, or orientation toward religion or religious beliefs.
  • B. religionOrBelief
    Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
  • C. religiousSpectrum
    Indicates a relationship that places entities along a range or continuum of religious belief, practice, or affiliation.
  • D. positionInReligion
    Indicates the specific role, rank, or office an entity holds within a religious organization or tradition.
  • E. religiousCounterpart
    Indicates that one entity serves as the religious equivalent or analogue of another entity within a different belief system or tradition.
  • F. None of above. chosen

Provenance (4 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_69f0ef878574819088c867fd1a5c8b86 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69fddf721c1481909301a0f379368f10 completed May 8, 2026, 1:04 p.m.
PD Predicate disambiguation batch_69fddda1ae7c8190b5848ff9a9e39826 completed May 8, 2026, 12:57 p.m.
PDg Predicate description generation batch_69fddf70ab10819088b76bd98e208354 completed May 8, 2026, 1:04 p.m.
Created at: April 28, 2026, 8:48 p.m.