Triple
T38010989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mrs. Bardell |
E948362
|
entity |
| Predicate | initiatesLegalActionAgainst |
P89736
|
FINISHED |
| Object | Samuel Pickwick |
—
|
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: Samuel Pickwick | Statement: [Mrs. Bardell, initiatesLegalActionAgainst, Samuel Pickwick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiatesLegalActionAgainst Context triple: [Mrs. Bardell, initiatesLegalActionAgainst, Samuel Pickwick]
-
A.
legalActionFiled
chosen
Indicates that a formal legal proceeding or complaint has been officially initiated with the appropriate authority or court.
-
B.
legalActionReason
Indicates the reason, cause, or grounds for which a particular legal action is initiated or taken.
-
C.
allegedAction
Indicates that an action is claimed or asserted to have occurred, typically without being proven or confirmed.
-
D.
seeksJusticeAgainst
Indicates that one entity actively pursues legal or moral accountability or retribution directed at another entity.
-
E.
mayProsecute
Indicates that one party has the legal authority or permission to initiate and conduct prosecution against another party.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:20 p.m.