Triple
T7602679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holbrook |
E180022
|
entity |
| Predicate | hasNotableBearer |
P458
|
FINISHED |
| Object |
Charles Holbrook
Charles Holbrook is a person notable enough to be recognized as a prominent bearer of the surname Holbrook.
|
E691815
|
NE FINISHED |
How this triple was built (4 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: Charles Holbrook | Statement: [Holbrook, hasNotableBearer, Charles Holbrook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Charles Holbrook Context triple: [Holbrook, hasNotableBearer, Charles Holbrook]
-
A.
George Holbrook
George Holbrook was an American clockmaker and bell founder known for producing church bells and tower clocks in the 19th century.
-
B.
Robert Holbrook
Robert Holbrook is a person notable enough to be recognized as a distinguished bearer of the surname Holbrook.
-
C.
Frank Holbrook
Frank Holbrook is a relatively obscure individual whose primary current distinction is being recorded as a notable bearer of the surname Holbrook.
-
D.
Philip Holbrook
Philip Holbrook is an individual notable enough to be recognized as a prominent bearer of the surname Holbrook.
-
E.
Joseph Holbrook
Joseph Holbrook is a relatively obscure individual whose name is notably associated with the surname Holbrook but who has no widely documented public prominence.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Charles Holbrook Triple: [Holbrook, hasNotableBearer, Charles Holbrook]
Generated description
Charles Holbrook is a person notable enough to be recognized as a prominent bearer of the surname Holbrook.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Charles Holbrook Target entity description: Charles Holbrook is a person notable enough to be recognized as a prominent bearer of the surname Holbrook.
-
A.
George Holbrook
George Holbrook was an American clockmaker and bell founder known for producing church bells and tower clocks in the 19th century.
-
B.
Robert Holbrook
Robert Holbrook is a person notable enough to be recognized as a distinguished bearer of the surname Holbrook.
-
C.
Frank Holbrook
Frank Holbrook is a relatively obscure individual whose primary current distinction is being recorded as a notable bearer of the surname Holbrook.
-
D.
Philip Holbrook
Philip Holbrook is an individual notable enough to be recognized as a prominent bearer of the surname Holbrook.
-
E.
Joseph Holbrook
Joseph Holbrook is a relatively obscure individual whose name is notably associated with the surname Holbrook but who has no widely documented public prominence.
- F. None of above. chosen
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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9fa633081909660f653f5b073cd |
completed | March 27, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c9abd319048190a24be5112c810489 |
completed | March 29, 2026, 10:46 p.m. |
| NEDg | Description generation | batch_69c9b01b23048190a4805947dd403cd8 |
completed | March 29, 2026, 11:04 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69c9b080ab4c8190a8d69dc9fee80510 |
completed | March 29, 2026, 11:06 p.m. |
Created at: March 27, 2026, 3:54 p.m.