Triple
T8773194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerala Legislative Assembly |
E208513
|
entity |
| Predicate | monsoonSession |
P43094
|
FINISHED |
| Object | held annually |
—
|
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: held annually | Statement: [Kerala Legislative Assembly, monsoonSession, held annually]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monsoonSession Context triple: [Kerala Legislative Assembly, monsoonSession, held annually]
-
A.
sessionScope
Indicates that a variable, resource, or configuration is associated with and persists for the duration of a single user session.
-
B.
sessionOf
chosen
Indicates that one entity is a session that belongs to, occurs within, or is associated with another entity (such as an event, course, or meeting series).
-
C.
sessionContext
Indicates the contextual relationship in which a session occurs, including its surrounding conditions, parameters, or environment that shape or influence that session.
-
D.
sessionNotation
Indicates a notation or labeling that is specifically associated with a particular session or occurrence of an event.
-
E.
lastSession
Indicates that one session is the final or most recent session associated with a given entity or sequence of sessions.
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f2dc87c8190be0597a260d95a0b |
completed | March 31, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:41 p.m.