Triple
T1645874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Assembly of Pakistan |
E35579
|
entity |
| Predicate | meetsInSessionType |
P983
|
FINISHED |
| Object | regular sessions |
—
|
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: regular sessions | Statement: [National Assembly of Pakistan, meetsInSessionType, regular sessions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsInSessionType Context triple: [National Assembly of Pakistan, meetsInSessionType, regular sessions]
-
A.
meetsBetweenSessionsOf
Indicates that one entity meets another during the interval between scheduled sessions or events.
-
B.
sessionType
chosen
Indicates the classification or category of a particular session based on its purpose, format, or context.
-
C.
meetsAs
Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
-
D.
meetsEvery
Indicates that one entity encounters or comes into contact with every member of a specified set of entities.
-
E.
meetsBy
Indicates that one entity encounters or comes together with another entity, typically at a specific time or place.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a919306fd48190a245fc95e0e759d9 |
completed | March 5, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69a907cc9d348190b76b0d3f596e5a81 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.