Triple

T5115266
Position Surface form Disambiguated ID Type / Status
Subject Community Affairs Bureau E115315 entity
Predicate mayCoordinateWith P34786 FINISHED
Object local community organizations 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: local community organizations | Statement: [Community Affairs Bureau, mayCoordinateWith, local community organizations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayCoordinateWith
Context triple: [Community Affairs Bureau, mayCoordinateWith, local community organizations]
  • A. coordinatedWith
    Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
  • B. mayMeet
    Indicates that one entity is permitted or has the possibility to meet or come together with another entity.
  • C. mayEngageIn chosen
    Indicates that one entity is permitted or authorized to participate in or perform a particular activity or interaction with another entity.
  • D. canBeConvenedBy
    Indicates that an entity (such as a group, body, or meeting) may be formally brought together or assembled by a specified agent or authority.
  • E. mayConduct
    Indicates that one entity is permitted or authorized to carry out, perform, or execute a particular action, process, or operation on or with 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_69bd4441d1648190a54a533895041987 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd75ce6044819094166aebf0688665 completed March 20, 2026, 4:29 p.m.
PD Predicate disambiguation batch_69bd7160d44081908cc64f3c14d28b81 completed March 20, 2026, 4:10 p.m.
Created at: March 20, 2026, 1:41 p.m.