Triple

T3802542
Position Surface form Disambiguated ID Type / Status
Subject San Francisco Office of the City Attorney E91722 entity
Predicate hasLegalAuthorityType P24006 FINISHED
Object civil 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: civil | Statement: [San Francisco Office of the City Attorney, hasLegalAuthorityType, civil]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLegalAuthorityType
Context triple: [San Francisco Office of the City Attorney, hasLegalAuthorityType, civil]
  • A. hasLegalAuthorityFrom
    Indicates that one entity possesses formal legal power, rights, or authorization that originates from or is granted by another entity.
  • B. legalAuthorityType chosen
    Indicates the specific kind or category of legal authority that governs, authorizes, or regulates an entity or action.
  • C. hasPublicAuthorityType
    Indicates that an entity possesses a specific type or category of public authority status or role.
  • D. hasLegalRole
    Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
  • E. legalAuthorityOver
    Indicates that one entity has the recognized power or right to make, enforce, or adjudicate rules or decisions concerning another entity.
  • 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_69aed96354f48190a768966d6bd19b04 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aee8db8a288190afd1e3b9dcf02e97 completed March 9, 2026, 3:35 p.m.
PD Predicate disambiguation batch_69aee7461abc8190945716f4b93e1a18 completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:15 p.m.