Triple

T7112180
Position Surface form Disambiguated ID Type / Status
Subject Public Law 111-84, Division E E165731 entity
Predicate expandsProtectionTo P9292 FINISHED
Object gender 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: gender | Statement: [Public Law 111-84, Division E, expandsProtectionTo, gender]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: expandsProtectionTo
Context triple: [Public Law 111-84, Division E, expandsProtectionTo, gender]
  • A. expandedProtectionTo chosen
    Indicates that an existing protection, safeguard, or coverage was broadened to include an additional entity, group, area, or scope.
  • B. addsProtectionFor
    Indicates that one entity provides or increases protective measures or safeguards for another entity.
  • C. permitsExpansionOf
    Indicates that one entity authorizes or enables the enlargement, extension, or increase in scope of another entity.
  • D. supportedExpansionOf
    Indicates that one entity actively aided, endorsed, or facilitated the growth, extension, or enlargement of another entity or domain.
  • E. restrictedExpansionOf
    Indicates a relationship where one entity is an expansion of another, but with added constraints or limitations that make it more specific or narrowly applicable than the original.
  • 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_69c6888120f081908f8f01b201dc4a4c completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e5edf89c8190a069b35ff7768165 completed March 27, 2026, 8:17 p.m.
PD Predicate disambiguation batch_69c6e1c4f9788190830288d00cc37026 completed March 27, 2026, 8 p.m.
Created at: March 27, 2026, 2:43 p.m.