Triple

T27999971
Position Surface form Disambiguated ID Type / Status
Subject To Have or To Be? E707120 entity
Predicate originalTitle P65 FINISHED
Object Haben oder Sein
Haben oder Sein is a philosophical and psychological work by Erich Fromm that contrasts materialistic, possession-based living with a more authentic, being-centered mode of existence.
E1800154 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: Haben oder Sein | Statement: [To Have or To Be?, originalTitle, Haben oder Sein]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Haben oder Sein
Triple: [To Have or To Be?, originalTitle, Haben oder Sein]
Generated description
Haben oder Sein is a philosophical and psychological work by Erich Fromm that contrasts materialistic, possession-based living with a more authentic, being-centered mode of existence.

Provenance (5 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_69ef96b980d88190a753b2f9a978595a completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69f63baed07c8190a48e5911fc8b270b completed May 2, 2026, 6 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15b8968a148190911a6a883be33be4 completed May 26, 2026, 3:13 p.m.
NEDg Description generation batch_6a15bacbff6c819090677517d3a16c61 completed May 26, 2026, 3:22 p.m.
NED2 Entity disambiguation (via description) batch_6a15bbd99e648190a306d2b62654a4d7 completed May 26, 2026, 3:27 p.m.
Created at: April 27, 2026, 7:56 p.m.