Triple

T33015052
Position Surface form Disambiguated ID Type / Status
Subject Brikama E844752 entity
Predicate hasLocalGovernmentArea P8215 FINISHED
Object Brikama Local Government Area
Brikama Local Government Area is an administrative region in western Gambia that encompasses the town of Brikama and its surrounding settlements.
E2032659 NE 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: Brikama Local Government Area | Statement: [Brikama, hasLocalGovernmentArea, Brikama Local Government Area]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Brikama Local Government Area
Triple: [Brikama, hasLocalGovernmentArea, Brikama Local Government Area]
Generated description
Brikama Local Government Area is an administrative region in western Gambia that encompasses the town of Brikama and its surrounding settlements.

Provenance (5 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_69f3494f3b4081909dccf2af34372a26 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d2aac5a081908f4dbb967eddfa3f completed May 3, 2026, 4:44 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34dad53b58819081a0938277e22b89 completed June 19, 2026, 5:59 a.m.
NEDg Description generation batch_6a34db8b54248190bbae5ab7444e5a08 completed June 19, 2026, 6:02 a.m.
NED2 Entity disambiguation (via description) batch_6a34dc8ff0b48190a6a9561683f13215 completed June 19, 2026, 6:07 a.m.
Created at: May 1, 2026, 1:23 a.m.