Triple
T18576589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benenson |
E454001
|
entity |
| Predicate | hasNotableBearer |
P458
|
FINISHED |
| Object |
Aaron Benenson
Aaron Benenson is an individual notable enough to be recognized as a significant bearer of the surname Benenson.
|
E1340799
|
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: Aaron Benenson | Statement: [Benenson, hasNotableBearer, Aaron Benenson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aaron Benenson Context triple: [Benenson, hasNotableBearer, Aaron Benenson]
-
A.
Michael Benenson
Michael Benenson is an individual notable enough to be recognized as a bearer of the surname Benenson, though specific widely known public details about him are not clearly established.
-
B.
Adam Aaronson
Adam Aaronson is a member of the musical group High Speed Scene, known for its energetic rock sound.
-
C.
Mark Benenson
Mark Benenson is a notable individual recognized for his contributions significant enough to be distinctly associated with the surname Benenson.
-
D.
Jacob Benenson
Jacob Benenson is a notable individual recognized for achievements significant enough to be associated with the surname Benenson.
-
E.
Andrew Braunsberg
Andrew Braunsberg is a film producer best known for his work on the acclaimed 1979 satirical comedy-drama "Being There."
- 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: Aaron Benenson Triple: [Benenson, hasNotableBearer, Aaron Benenson]
Generated description
Aaron Benenson is an individual notable enough to be recognized as a significant bearer of the surname Benenson.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Aaron Benenson Target entity description: Aaron Benenson is an individual notable enough to be recognized as a significant bearer of the surname Benenson.
-
A.
Michael Benenson
Michael Benenson is an individual notable enough to be recognized as a bearer of the surname Benenson, though specific widely known public details about him are not clearly established.
-
B.
Adam Aaronson
Adam Aaronson is a member of the musical group High Speed Scene, known for its energetic rock sound.
-
C.
Mark Benenson
Mark Benenson is a notable individual recognized for his contributions significant enough to be distinctly associated with the surname Benenson.
-
D.
Jacob Benenson
Jacob Benenson is a notable individual recognized for achievements significant enough to be associated with the surname Benenson.
-
E.
Andrew Braunsberg
Andrew Braunsberg is a film producer best known for his work on the acclaimed 1979 satirical comedy-drama "Being There."
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543cc94f081909b76c3d488ed5637 |
completed | April 19, 2026, 9:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0532449aec81908a6ab931ca69394b |
completed | May 14, 2026, 2:24 a.m. |
| NEDg | Description generation | batch_6a0536bdc79081909dd99b221110f6b2 |
completed | May 14, 2026, 2:43 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a053766f7b48190b3b01ee99b22f57d |
completed | May 14, 2026, 2:45 a.m. |
Created at: April 10, 2026, 11:43 a.m.