Triple
T3331210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E. E. Cummings |
E70036
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | Him |
E185703
|
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: Him | Statement: [E. E. Cummings, notableWork, Him]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Him Context triple: [E. E. Cummings, notableWork, Him]
-
A.
He
He is a common Chinese surname borne by numerous notable figures across politics, military, arts, and academia.
-
B.
Him (song)
chosen
"Him" is a 1979 soft rock hit by singer-songwriter Rupert Holmes, best known as one of his major chart successes alongside "Escape (The Piña Colada Song)."
-
C.
Hein
Hein is a Dutch surname most notably borne by Piet Hein, a renowned 17th-century naval officer and folk hero of the Dutch Republic.
-
D.
Han
Han is a common transliteration of the historical Central Asian title "Khan," often associated with rulers and nobility in various Turkic and Mongolic cultures.
-
E.
Wem
Wem is a small market town and civil parish in the county of Shropshire, England.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb191e1988190a1d88596f6605aff |
completed | March 8, 2026, 5:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b31a841c608190942e040c14f560d2 |
completed | March 12, 2026, 7:56 p.m. |
Created at: March 8, 2026, 3:12 p.m.