Triple
T14753549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London congestion charging zone |
E346673
|
entity |
| Predicate | penaltyForNonPayment |
P1841
|
FINISHED |
| Object | penalty charge notice |
—
|
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: penalty charge notice | Statement: [London congestion charging zone, penaltyForNonPayment, penalty charge notice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: penaltyForNonPayment Context triple: [London congestion charging zone, penaltyForNonPayment, penalty charge notice]
-
A.
defaultPenalty
Indicates that a standard or automatically applied penalty is imposed in the absence of a specific or overridden penalty.
-
B.
penaltyProvision
chosen
Indicates that a rule, contract, or law includes a clause specifying a punishment or sanction for non-compliance or violation.
-
C.
penaltyMechanism
Indicates a relationship where a rule, system, or process imposes a negative consequence or sanction in response to certain actions or conditions.
-
D.
penaltyReducedTo
Indicates that an existing penalty has been lowered or commuted to a lesser penalty or amount.
-
E.
penaltyOrder
Indicates that an authority has issued a formal decision imposing a penalty or sanction on a 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d59df08190a86da5048358bd6e |
completed | April 14, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.