Triple
T5334371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Derek |
E123789
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Derek |
E80773
|
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: Derek | Statement: [John Derek, familyName, Derek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Derek Context triple: [John Derek, familyName, Derek]
-
A.
Derek
chosen
Derek is a masculine given name of English origin commonly used in the United States and other English-speaking countries.
-
B.
Derek Charles
Derek Charles is the successful corporate executive whose life unravels when he becomes the target of a coworker’s dangerous obsession in the 2009 thriller film "Obsessed."
-
C.
Derek Bond
Derek Bond was a British actor known for his work in mid-20th-century film, television, and theatre.
-
D.
Derek Martinus
Derek Martinus was a British television director best known for his work on classic "Doctor Who" serials during the 1960s.
-
E.
Derek Austin
Derek Austin is a British information scientist and librarian best known for his work in classification theory and contributions to the development of library and information retrieval systems.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85ae52c08190968a5567b7e6b794 |
completed | March 20, 2026, 5:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf18baeca081909acc11d0c6c89f6d |
completed | March 21, 2026, 10:16 p.m. |
Created at: March 20, 2026, 2 p.m.