Triple

T16598954
Position Surface form Disambiguated ID Type / Status
Subject Professional and Amateur Sports Protection Act E403281 entity
Predicate restrictedEntity P1050 FINISHED
Object states 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: states | Statement: [Professional and Amateur Sports Protection Act, restrictedEntity, states]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: restrictedEntity
Context triple: [Professional and Amateur Sports Protection Act, restrictedEntity, states]
  • A. restrictedRight
    Indicates that an entity’s ability to exercise a particular right is limited, constrained, or subject to specific conditions or prohibitions.
  • B. 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.
  • C. boundEntity
    Indicates that one entity is constrained, tied, or otherwise held in a fixed relationship or dependency to another entity.
  • D. distributionRestricted
    Indicates that the distribution or sharing of something is limited or controlled by specific restrictions or conditions.
  • E. restrictionLevel
    Indicates the degree or strictness of limitations or constraints imposed on an entity, action, or access.
  • 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_69d883880d0c81908b5fcd454e767b60 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e35d74738c81909711654cf38af150 completed April 18, 2026, 10:31 a.m.
PD Predicate disambiguation batch_69e296a7d9d0819088555bca6c936e79 completed April 17, 2026, 8:23 p.m.
Created at: April 10, 2026, 5:16 a.m.