Triple
T17238833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Mallon |
E418433
|
entity |
| Predicate | violatedCondition |
P2111
|
FINISHED |
| Object | resumed work as a cook under assumed names |
—
|
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: resumed work as a cook under assumed names | Statement: [Mary Mallon, violatedCondition, resumed work as a cook under assumed names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: violatedCondition Context triple: [Mary Mallon, violatedCondition, resumed work as a cook under assumed names]
-
A.
violationOf
Indicates that one entity breaches, disobeys, or infringes upon a rule, law, agreement, or right associated with another entity.
-
B.
violatedPrinciple
chosen
Indicates that an entity has broken, disregarded, or acted contrary to a specified rule, norm, or guiding principle.
-
C.
assertedViolationOf
Indicates that one party has formally claimed or alleged that a rule, law, standard, or obligation has been violated.
-
D.
violationContext
Indicates the specific circumstances, conditions, or situational factors under which a violation occurs or is considered to have occurred.
-
E.
unsatisfiableRangeCondition
Indicates that a specified range condition cannot be met because its constraints are logically inconsistent or impossible to satisfy.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dfdc8688190aceb223c19a48781 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.