Triple
T439824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Espionage Act of 1917 |
E10089
|
entity |
| Predicate | maximumPenalty |
P1841
|
FINISHED |
| Object | death in certain cases |
—
|
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: death in certain cases | Statement: [Espionage Act of 1917, maximumPenalty, death in certain cases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumPenalty Context triple: [Espionage Act of 1917, maximumPenalty, death in certain cases]
-
A.
penaltyProvision
chosen
Indicates that a rule, contract, or law includes a clause specifying a punishment or sanction for non-compliance or violation.
-
B.
maximumDraft
Indicates that there is an upper limit on the number of drafts that can be created, stored, or associated with a given entity or process.
-
C.
maxCurrent
Indicates the maximum electric current that is allowed to flow through or be drawn by an entity under specified conditions.
-
D.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
E.
maximumBondMaturity
Indicates the longest allowable or actual time period until a bond tied to an entity reaches its maturity date.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef2977888190a0590b2c1bd2f5da |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddcf50c8190bfa0d1f8ee9f604a |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.