Triple
T27963079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tripura Legislative Assembly |
E704635
|
entity |
| Predicate | becameStateLegislatureOn |
P64528
|
FINISHED |
| Object | 21 January 1972 |
—
|
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: 21 January 1972 | Statement: [Tripura Legislative Assembly, becameStateLegislatureOn, 21 January 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameStateLegislatureOn Context triple: [Tripura Legislative Assembly, becameStateLegislatureOn, 21 January 1972]
-
A.
establishedAsProvincialLegislature
chosen
Indicates that an entity has been formally created or designated to function as a provincial-level legislative body.
-
B.
legislatureServed
Indicates that an individual has served as a member of a specific legislative body during some period of time.
-
C.
legislatureFormed
Indicates that a legislative body has been officially created or constituted for a given political entity or jurisdiction.
-
D.
stateLegislativeBodyServedIn
Indicates the specific state-level legislative body in which an individual has served as a member.
-
E.
isPartOfStateLegislature
Indicates that an entity serves as a member or component within a specific state-level legislative body.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b04d0788190b179fe981de41fff |
completed | May 2, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:33 p.m.