Triple

T24863130
Position Surface form Disambiguated ID Type / Status
Subject Sea Mills E622206 entity
Predicate withinAuthority P49097 FINISHED
Object Bristol City Council NE NERFINISHED

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: Bristol City Council | Statement: [Sea Mills, withinAuthority, Bristol City Council]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: withinAuthority
Context triple: [Sea Mills, withinAuthority, Bristol City Council]
  • A. authorityWithin
    Indicates that one entity holds recognized power, control, or decision-making authority inside the scope, domain, or jurisdiction defined by another entity.
  • B. underDirectAuthorityOf
    Indicates that one entity is directly controlled, supervised, or governed by another entity with no intermediary authority in between.
  • C. usesAuthorityOf
    Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
  • D. areaOfAuthority chosen
    Indicates the domain, region, or scope within which an entity has official power, control, or responsibility.
  • E. hasLimitedAuthorityOver
    Indicates that one entity holds a constrained or partial power to direct, control, or make decisions about another entity, but not full or unrestricted authority.
  • 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_69e2fac350d08190b3affde1b451a8c5 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f44a417a58819081777e18dda149fd completed May 1, 2026, 6:37 a.m.
PD Predicate disambiguation batch_69f442b8479c8190a7c8e416ac9e28a0 completed May 1, 2026, 6:05 a.m.
Created at: April 18, 2026, 5:22 a.m.