Triple
T34981369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul (Die tote Stadt) |
E1008822
|
entity |
| Predicate | housekeeper |
P68145
|
FINISHED |
| Object | Brigitta (Die tote Stadt) |
—
|
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: Brigitta (Die tote Stadt) | Statement: [Paul (Die tote Stadt), housekeeper, Brigitta (Die tote Stadt)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: housekeeper Context triple: [Paul (Die tote Stadt), housekeeper, Brigitta (Die tote Stadt)]
-
A.
householdStaff
chosen
Indicates that one entity serves as domestic or household staff for another entity, typically within a private residence.
-
B.
housekeeperPraises
Indicates that a housekeeper expresses approval or commendation toward someone or something.
-
C.
household
Indicates that two or more entities belong to or are part of the same household unit, typically sharing a residence and domestic life.
-
D.
houseRole
Indicates the functional role, purpose, or use that a house has within a given context or system.
-
E.
houseHead
Indicates that one entity serves as the head, leader, or primary authority of a particular house or household associated with the other 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.