Triple
T10175960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rufus Sewell |
E235851
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | Zen |
E494483
|
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: Zen | Statement: [Rufus Sewell, notableWork, Zen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zen Context triple: [Rufus Sewell, notableWork, Zen]
-
A.
Zen
Zen is AMD's high-performance x86 CPU microarchitecture that underpins its modern EPYC server processors and Ryzen desktop chips.
-
B.
Zen
chosen
Zen is a British television crime drama series based on Michael Dibdin’s Aurelio Zen detective novels, produced by Left Bank Pictures.
-
C.
Zen-Whoberian
Zen-Whoberians are a fictional alien humanoid species in the Marvel universe, best known through the character Gamora and characterized by their green skin, enhanced physical abilities, and warrior culture.
-
D.
ZEN
ZEN is the stock ticker symbol for Zendesk, a customer service and engagement software company.
-
E.
Zen koans
Zen koans are paradoxical anecdotes or riddles used in Zen Buddhism as meditation tools to transcend logical thinking and provoke direct insight into reality.
- 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_69ca84d1d5f88190ab878a1021ecff68 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdecd3a2688190bce277bffffcbf8b |
completed | April 2, 2026, 4:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d301232e5c8190ad80c4e78681994c |
completed | April 6, 2026, 12:41 a.m. |
Created at: March 30, 2026, 9:11 p.m.