Triple
T26199310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assam Accord |
E655188
|
entity |
| Predicate | assamMovementStartYear |
P160034
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [Assam Accord, assamMovementStartYear, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assamMovementStartYear Context triple: [Assam Accord, assamMovementStartYear, 1979]
-
A.
armedStruggleStart
Indicates the point in time when an organized group initiates the use of armed force or violence as a method of struggle or conflict.
-
B.
armedStrugglePeriod
Indicates a period during which a group or movement engages in organized, sustained use of armed force to pursue its political or ideological objectives.
-
C.
involvedIndependenceMovement
Indicates that an entity actively participated in or contributed to an independence movement seeking political or national self-determination.
-
D.
firstMajorUprisingEndDate
Indicates the date on which the first major uprising associated with the subject came to an end.
-
E.
uprisingDate
Indicates the date on which an uprising or rebellion occurred or began.
- F. None of above. chosen
Provenance (4 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cd9e50481908d1559e6ec048bc1 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:47 p.m.