Triple

T24817869
Position Surface form Disambiguated ID Type / Status
Subject Futures Trading Practices Act of 1992 E620973 entity
Predicate regulatesEntityType P98581 FINISHED
Object futures commission merchants 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: futures commission merchants | Statement: [Futures Trading Practices Act of 1992, regulatesEntityType, futures commission merchants]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regulatesEntityType
Context triple: [Futures Trading Practices Act of 1992, regulatesEntityType, futures commission merchants]
  • A. hasRegulatedEntityType chosen
    Indicates that an entity is subject to regulation specifically because it belongs to a particular regulated category or type.
  • B. supportsEntityType
    Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of entity.
  • C. includedEntityType
    Indicates that one entity type is contained within, or forms a component part of, another entity type.
  • D. regulatoryType
    Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
  • E. documentedEntityType
    Indicates that an entity has been documented as belonging to a specific type or category.
  • 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_69e2fabfd4648190bd0e5c7f4dbb6cab completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f55e519978819087a1676564a74630 completed May 2, 2026, 2:15 a.m.
PD Predicate disambiguation batch_69f4a0edd10c81908a052ab864d57c54 completed May 1, 2026, 12:47 p.m.
Created at: April 18, 2026, 5:03 a.m.