Triple
T11950176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hunting of the Snark |
E284405
|
entity |
| Predicate | featuresCharacter |
P626
|
FINISHED |
| Object | the Bellman |
E436289
|
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: the Bellman | Statement: [The Hunting of the Snark, featuresCharacter, the Bellman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: the Bellman Context triple: [The Hunting of the Snark, featuresCharacter, the Bellman]
-
A.
Bellman
chosen
Bellman is a surname most prominently associated with New Zealand-born British actress Gina Bellman, known for her roles in television and film.
-
B.
Floyd
Floyd is a track from the soundtrack of the video game "Food."
-
C.
Floyd
Floyd is a masculine given name of Welsh origin, commonly used in English-speaking countries.
-
D.
Bregman
Bregman is a surname most prominently associated with American professional baseball player Alex Bregman of the Houston Astros.
-
E.
Berman
Berman is a surname of Ashkenazi Jewish origin borne by various notable individuals across fields such as art, politics, and academia.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90364c2608190a3946c9595c71164 |
completed | April 10, 2026, 2:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f458f16f088190a0005ff0fd4f547f |
completed | May 1, 2026, 7:40 a.m. |
Created at: April 8, 2026, 9:45 p.m.