Triple
T28782794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Denisovich Shukhov |
E726718
|
entity |
| Predicate | hasFullNameInTitle |
P145831
|
FINISHED |
| Object | One Day in the Life of Ivan Denisovich |
—
|
NE NERFINISHED |
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: One Day in the Life of Ivan Denisovich | Statement: [Ivan Denisovich Shukhov, hasFullNameInTitle, One Day in the Life of Ivan Denisovich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFullNameInTitle Context triple: [Ivan Denisovich Shukhov, hasFullNameInTitle, One Day in the Life of Ivan Denisovich]
-
A.
hasGivenNameInTitle
chosen
Indicates that the given name of an entity appears within the title of another entity.
-
B.
hasTitleInName
Indicates that an entity’s name explicitly includes a specified title as part of it.
-
C.
hasTitleName
Indicates that an entity possesses or is associated with a specific title or name.
-
D.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
E.
hasNameInCaseTitle
Indicates that a legal case’s title explicitly contains the name of the referenced entity.
- F. None of above.
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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 6:20 a.m.