Triple

T5732662
Position Surface form Disambiguated ID Type / Status
Subject IEEE Bylaws E126419 entity
Predicate hasLegalStatusAs P2250 FINISHED
Object internal governing rules of IEEE 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: internal governing rules of IEEE | Statement: [IEEE Bylaws, hasLegalStatusAs, internal governing rules of IEEE]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLegalStatusAs
Context triple: [IEEE Bylaws, hasLegalStatusAs, internal governing rules of IEEE]
  • A. hasLegalStatus chosen
    Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
  • B. hasSpecialLegalStatus
    Indicates that an entity possesses a distinct, formally recognized legal standing or set of rights and obligations that differs from the standard legal status of comparable entities.
  • C. hasLegalAuthorityFrom
    Indicates that one entity possesses formal legal power, rights, or authorization that originates from or is granted by another entity.
  • D. hasLegalRank
    Indicates that an entity holds a specific legal status, classification, or rank within a formal legal or regulatory system.
  • E. hasLegalForceIn
    Indicates that something (such as a law, regulation, or agreement) is legally valid, binding, and enforceable within a specified jurisdiction or context.
  • 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_69c0083082288190b7478cead6b5430a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c029014588819094a2a0f6f9b66bab completed March 22, 2026, 5:38 p.m.
PD Predicate disambiguation batch_69c021c6488881909bed4a4534d57f70 completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:47 p.m.