Triple

T537715
Position Surface form Disambiguated ID Type / Status
Subject MIT Club Judo E12362 entity
Predicate safetyEmphasis P12725 FINISHED
Object controlled practice environment 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: controlled practice environment | Statement: [MIT Club Judo, safetyEmphasis, controlled practice environment]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: safetyEmphasis
Context triple: [MIT Club Judo, safetyEmphasis, controlled practice environment]
  • A. safety chosen
    Indicates that an entity provides, ensures, or is associated with protection from harm, danger, or risk for another entity or within a given context.
  • B. aimsToProtect
    Indicates an intention or purpose to safeguard or defend one entity, value, or condition from harm, risk, or undesirable outcomes.
  • C. protects
    Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
  • D. securityArrangementsBy
    Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
  • E. ensures
    Indicates that one entity guarantees or makes certain that a particular condition, outcome, or state holds for another entity or situation.
  • F. None of above.

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_69a4933208e88190891f5debab1b776d completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4985e51908190a34aa82ea9dbee1e completed March 1, 2026, 7:49 p.m.
PD Predicate disambiguation batch_69a494b51ff08190a39f4168fd9a7ddf completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:32 p.m.