Triple
T11698866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahalwari system |
E278067
|
entity |
| Predicate | collectionResponsibility |
P87654
|
FINISHED |
| Object | village headmen |
—
|
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 headmen | Statement: [Mahalwari system, collectionResponsibility, village headmen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionResponsibility Context triple: [Mahalwari system, collectionResponsibility, village headmen]
-
A.
collectionRole
Indicates the specific function, responsibility, or position an entity holds within a collection or grouped set of items.
-
B.
collectionRepository
Indicates a relationship where a repository is responsible for storing, managing, or providing access to a collection.
-
C.
collectionFormed
Indicates that multiple items or entities have been gathered and organized together into a defined collection.
-
D.
collectionScope
Indicates the extent, boundaries, or range over which a collection (such as a set of items, data, or resources) is defined or intended to apply.
-
E.
collectionBy
chosen
Indicates that one entity is the collector or curator responsible for assembling, managing, or owning a particular collection of items represented by another entity.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47df68c81908a91919a69b4880d |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.