Triple
T3142640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champaran |
E65685
|
entity |
| Predicate | issueOfMovement |
P29037
|
FINISHED |
| Object | exploitation of indigo cultivators |
—
|
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: exploitation of indigo cultivators | Statement: [Champaran, issueOfMovement, exploitation of indigo cultivators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issueOfMovement Context triple: [Champaran, issueOfMovement, exploitation of indigo cultivators]
-
A.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
B.
notableMovementType
Indicates the type or category of significant movement or motion associated with an entity.
-
C.
involvesIssue
chosen
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
-
D.
issue
Indicates that an entity formally publishes, releases, or distributes something, such as a document, statement, or item, often in an official or authoritative capacity.
-
E.
broaderMovement
Indicates that one movement is a more general, encompassing movement within which another, more specific movement is situated.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada579b07c8190a7b316f499911a2d |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.