Triple
T3656277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Consumer Credit Protection Act 2009 |
E77537
|
entity |
| Predicate | commenced |
P19545
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [National Consumer Credit Protection Act 2009, commenced, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commenced Context triple: [National Consumer Credit Protection Act 2009, commenced, 2010]
-
A.
began
chosen
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
B.
committed
Indicates that an agent has carried out or been responsible for a specific act, event, or wrongdoing.
-
C.
commissioned
Indicates that one entity formally authorized or ordered another entity to create, produce, or carry out something, often in exchange for payment or obligation.
-
D.
occupationBegan
Indicates the point in time when an entity started holding a particular occupation or job.
-
E.
commutation
Indicates the legal action of reducing, altering, or substituting a previously imposed penalty or obligation, typically making it less severe while preserving the underlying judgment or relationship.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3bc2b408190a3a51f9cde5a03b5 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.