Triple

T28735583
Position Surface form Disambiguated ID Type / Status
Subject Oakland City Council District 4 E730788 entity
Predicate containsNeighborhood P4813 FINISHED
Object Lincoln Highlands
Lincoln Highlands is a residential neighborhood in the Oakland hills of California known for its quiet streets and hillside views.
E1830650 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: Lincoln Highlands | Statement: [Oakland City Council District 4, containsNeighborhood, Lincoln Highlands]
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: Lincoln Highlands
Triple: [Oakland City Council District 4, containsNeighborhood, Lincoln Highlands]
Generated description
Lincoln Highlands is a residential neighborhood in the Oakland hills of California known for its quiet streets and hillside views.

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_69f043eae0908190b28ce314686247d7 completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69f6576b53a081908be86f12b54a1945 completed May 2, 2026, 7:58 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1ccf66d2ac81909c27c80751bd7fab completed June 1, 2026, 12:16 a.m.
NEDg Description generation batch_6a1cd02268a88190b51b5602e6916d3e completed June 1, 2026, 12:19 a.m.
NED2 Entity disambiguation (via description) batch_6a249466d5b08190bd3886ef517cb367 completed June 6, 2026, 9:43 p.m.
Created at: April 28, 2026, 6 a.m.