Triple
T16450306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benjamin Jonson |
E399533
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Benjamin |
E399533
|
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: Benjamin | Statement: [Benjamin Jonson, givenName, Benjamin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Benjamin Context triple: [Benjamin Jonson, givenName, Benjamin]
-
A.
Benjamin
Benjamin is the naive, dream-filled protagonist of Mendele Mocher Sforim’s satirical Yiddish novel "The Travels of Benjamin the Third," often likened to a Jewish Don Quixote.
-
B.
Benjamin
chosen
Benjamin is the full given name of the English playwright and poet Ben Jonson, a major literary figure of the early 17th century.
-
C.
Benjamin
Benjamin is a surname of Hebrew origin commonly used in many cultures and languages.
-
D.
Benjamin
Benjamin is the given name of Benjamin Clémentine, the English artist known for his work as a singer, songwriter, and poet.
-
E.
Benjamin
Benjamin is the given first name of the American film producer and studio executive B. P. Schulberg.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32cdfb0ec8190b75c4e6f4aceb200 |
completed | April 18, 2026, 7:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0045872a688190bcab27c6a2b952cd |
completed | May 10, 2026, 8:44 a.m. |
Created at: April 10, 2026, 5:10 a.m.