Triple
T9230002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian Buddenbrook |
E221790
|
entity |
| Predicate | failsToConformTo |
P87688
|
FINISHED |
| Object | bourgeois expectations |
—
|
LITERAL 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: bourgeois expectations | Statement: [Christian Buddenbrook, failsToConformTo, bourgeois expectations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failsToConformTo Context triple: [Christian Buddenbrook, failsToConformTo, bourgeois expectations]
-
A.
conformsTo
Indicates that one entity complies with, follows, or is in accordance with a specified standard, specification, rule, or guideline.
-
B.
notEnforcedBy
Indicates that a rule, policy, or obligation is not upheld, imposed, or carried out by the referenced enforcing entity.
-
C.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
D.
failsWhen
Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
-
E.
consistentWith
Indicates that one entity does not contradict and is compatible or in agreement with another entity, condition, or set of constraints.
- F. None of above. chosen
Provenance (4 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccee17a2dc8190b373f78be7247f0d |
completed | April 1, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:29 p.m.