Triple
T2203429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charter Act 1813 |
E50542
|
entity |
| Predicate | financialProvisionAmount |
P482
|
FINISHED |
| Object | 1 lakh rupees per year for education |
—
|
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: 1 lakh rupees per year for education | Statement: [Charter Act 1813, financialProvisionAmount, 1 lakh rupees per year for education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: financialProvisionAmount Context triple: [Charter Act 1813, financialProvisionAmount, 1 lakh rupees per year for education]
-
A.
monetaryValue
chosen
Indicates the amount of money associated with an entity, event, or transaction.
-
B.
paymentAmount
Indicates the specific monetary value involved in a payment transaction between parties.
-
C.
finType
Indicates that an entity is of a finite type, meaning it has only a finite number of distinct possible values or elements.
-
D.
hasMonetaryComponent
Indicates that something includes, involves, or is associated with a monetary or financial element.
-
E.
monetaryComponent
Indicates that something is a financial element or part of a larger monetary value, structure, or transaction.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfa481308190bda187c03162e0b6 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.