Triple
T25028331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Executive Order 6260 |
E626769
|
entity |
| Predicate | penaltyMaximumImprisonmentYears |
P53458
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Executive Order 6260, penaltyMaximumImprisonmentYears, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: penaltyMaximumImprisonmentYears Context triple: [Executive Order 6260, penaltyMaximumImprisonmentYears, 10]
-
A.
durationOfImprisonment
Indicates the length of time that an entity is or was held in imprisonment.
-
B.
imprisonmentYear
Indicates the specific year in which an entity was imprisoned or placed into custody.
-
C.
imprisonedFor
Indicates that one entity is held in detention or jail as a consequence of, or in connection with, a specific reason, action, or offense committed by another entity or itself.
-
D.
maximumImprisonmentPower
chosen
Indicates the highest duration or extent of imprisonment that an authority is legally empowered to impose.
-
E.
sentencingYear
Indicates the calendar year in which a person or entity received a formal legal sentence or judgment.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:07 a.m.