Triple
T29091577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scooter Libby |
E734865
|
entity |
| Predicate | fineStatus |
P127
|
FINISHED |
| Object | fine remained in effect after commutation |
—
|
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: fine remained in effect after commutation | Statement: [Scooter Libby, fineStatus, fine remained in effect after commutation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fineStatus Context triple: [Scooter Libby, fineStatus, fine remained in effect after commutation]
-
A.
fine
Indicates that an authority imposes a monetary penalty on an entity for violating a rule, law, or agreement.
-
B.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
C.
functionStatus
Indicates the operational state or condition of a function (e.g., active, inactive, pending, or failed) at a given time.
-
D.
feeStatus
Indicates the current state or condition of fees associated with an entity, such as whether they are due, paid, waived, or overdue.
-
E.
finish
Indicates that an entity brings an action, process, or state to an end or completion.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6617d89d08190ae38220244c07b1f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:05 a.m.