Triple
T13053871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint session of Uttar Pradesh Legislature |
E327515
|
entity |
| Predicate | occursAtLeast |
P84417
|
FINISHED |
| Object | once a year |
—
|
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: once a year | Statement: [Joint session of Uttar Pradesh Legislature, occursAtLeast, once a year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursAtLeast Context triple: [Joint session of Uttar Pradesh Legislature, occursAtLeast, once a year]
-
A.
meetsAtLeast
Indicates that one entity encounters or comes into contact with another entity at least a specified minimum number of times or to a minimum required degree.
-
B.
occursFor
Indicates that an event, process, or condition takes place in relation to, or on behalf of, a particular entity or context.
-
C.
occursAt
Indicates that an event or action takes place at a specific time or location.
-
D.
occursEvery
Indicates that an event or action happens repeatedly at regular, specified intervals.
-
E.
hasMinimum
chosen
Indicates that an entity possesses at least a specified lower bound or smallest allowable value, quantity, or level in relation to another entity or constraint.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:58 p.m.