Triple
T20649185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Bang financial reforms |
E507441
|
entity |
| Predicate | mainTypeOfReform |
P98268
|
FINISHED |
| Object | financial deregulation |
—
|
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: financial deregulation | Statement: [Big Bang financial reforms, mainTypeOfReform, financial deregulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTypeOfReform Context triple: [Big Bang financial reforms, mainTypeOfReform, financial deregulation]
-
A.
typeOfReforms
chosen
Indicates the specific kinds or categories of reforms associated with an entity or situation.
-
B.
goalOfReforms
Indicates that a reform or set of reforms is undertaken with the aim or intended objective of achieving a particular outcome.
-
C.
reform
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
D.
subjectToReformBy
Indicates that an entity is undergoing or designated for changes, improvements, or restructuring carried out by another entity.
-
E.
isPartOfReform
Indicates that an action, measure, or component belongs to, contributes to, or is included within a broader reform initiative or process.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6af2076b48190b9c8afb4eac65f46 |
completed | April 20, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.