Triple

T27184500
Position Surface form Disambiguated ID Type / Status
Subject Holcomb E683291 entity
Predicate hasNotableBearer P458 FINISHED
Object Charlie Holcomb
Charlie Holcomb is an individual notable enough to be recognized as a bearer of the Holcomb surname, though specific widely known public details about them are not well documented.
E1769673 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: Charlie Holcomb | Statement: [Holcomb, hasNotableBearer, Charlie Holcomb]
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: Charlie Holcomb
Triple: [Holcomb, hasNotableBearer, Charlie Holcomb]
Generated description
Charlie Holcomb is an individual notable enough to be recognized as a bearer of the Holcomb surname, though specific widely known public details about them are not well documented.

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_69eefad140408190b8586fdebcf9af46 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f6258005888190b9288f7fc40f23d0 completed May 2, 2026, 4:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12a7bd9eb08190a32eef8eb45ba617 completed May 24, 2026, 7:24 a.m.
NEDg Description generation batch_6a12a91cda148190b9d85ae8f9d24250 completed May 24, 2026, 7:30 a.m.
NED2 Entity disambiguation (via description) batch_6a12aa051060819082b52092cdccd0d5 completed May 24, 2026, 7:34 a.m.
Created at: April 27, 2026, 9:30 a.m.