Triple

T85164
Position Surface form Disambiguated ID Type / Status
Subject Glass–Steagall Act E1713 entity
Predicate restricted P1050 FINISHED
Object securities activities of commercial banks 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: securities activities of commercial banks | Statement: [Glass–Steagall Act, restricted, securities activities of commercial banks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: restricted
Context triple: [Glass–Steagall Act, restricted, securities activities of commercial banks]
  • A. restriction chosen
    Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
  • B. protectedIn
    Indicates that one entity is safeguarded, preserved, or kept safe within the context, environment, or jurisdiction of another entity.
  • C. prohibits
    Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
  • D. held
    Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
  • E. requires
    Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
  • 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_69a24c8150408190910a693eb51c1f71 completed Feb. 28, 2026, 2:01 a.m.
NER Named-entity recognition batch_69a250e401288190ba12322c9c5f07c9 completed Feb. 28, 2026, 2:20 a.m.
PD Predicate disambiguation batch_69a24eb59e808190811c20518f39b1cc completed Feb. 28, 2026, 2:11 a.m.
Created at: Feb. 28, 2026, 2:06 a.m.