Triple

T276915
Position Surface form Disambiguated ID Type / Status
Subject Trump University E5268 entity
Predicate closureReason P8451 FINISHED
Object legal and regulatory pressure 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: legal and regulatory pressure | Statement: [Trump University, closureReason, legal and regulatory pressure]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: closureReason
Context triple: [Trump University, closureReason, legal and regulatory pressure]
  • A. closureAnnouncedBy
    Indicates that an entity’s closure has been formally communicated or declared by a specified agent or source.
  • B. closed
    Indicates that an entity has brought something (such as an object, container, or space) from an open state into a shut or sealed state, or that it is currently in that shut state.
  • C. closingDoxology
    Indicates the concluding liturgical or devotional formula of praise that formally ends a prayer, hymn, or religious text.
  • D. cancellation
    Indicates that a previously planned or scheduled event, action, or agreement is being annulled, terminated, or rendered no longer valid.
  • E. closureContext
    Indicates the surrounding scope or environment in which an operation, expression, or function is defined and executed, capturing the variables and bindings available to it.
  • 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_69a257e6c8788190987dfe705ca2912a completed Feb. 28, 2026, 2:50 a.m.
NER Named-entity recognition batch_69a25ded68c88190b1fc595ce329aeb9 completed Feb. 28, 2026, 3:15 a.m.
PD Predicate disambiguation batch_69a25b7480e881909399beccfc7ffb81 completed Feb. 28, 2026, 3:05 a.m.
PDg Predicate description generation batch_69a25c2d94388190aeda17ddd42b4ac9 completed Feb. 28, 2026, 3:08 a.m.
Created at: Feb. 28, 2026, 2:59 a.m.