Triple
T37725209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation VII of 1822 (North-Western Provinces) |
E939698
|
entity |
| Predicate | revenuePayerType |
P23023
|
FINISHED |
| Object | village communities |
—
|
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: village communities | Statement: [Regulation VII of 1822 (North-Western Provinces), revenuePayerType, village communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revenuePayerType Context triple: [Regulation VII of 1822 (North-Western Provinces), revenuePayerType, village communities]
-
A.
payerType
chosen
Indicates the type or category of entity responsible for making a payment in the relationship.
-
B.
revenuePaidTo
Indicates that a specified amount of revenue is paid or transferred from one entity to another as a recipient.
-
C.
appliesToRevenueType
Indicates that a rule, condition, or classification is specifically relevant or applicable to a particular type of revenue.
-
D.
payType
Indicates the method or category of payment used in a transaction or compensation arrangement.
-
E.
payers
Indicates that certain entities make payments to, or are financially responsible for, other entities or obligations.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.