Triple
T2244274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish parliament |
E49465
|
entity |
| Predicate | openSessionsPolicy |
P1390
|
FINISHED |
| Object | generally public 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: generally public sessions | Statement: [Polish parliament, openSessionsPolicy, generally public sessions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openSessionsPolicy Context triple: [Polish parliament, openSessionsPolicy, generally public sessions]
-
A.
openAccessPolicy
chosen
Indicates that an entity has a policy allowing unrestricted or minimally restricted public access to its resources, content, or services.
-
B.
heldSessionsIn
Indicates that an entity organized or conducted one or more sessions, meetings, or events at a specified location or venue.
-
C.
openStatus
Indicates whether an entity (such as a place, service, or resource) is currently open or available for use.
-
D.
meetsBetweenSessionsOf
Indicates that one entity meets another during the interval between scheduled sessions or events.
-
E.
openedForCurrentUse
Indicates that an entity has been opened and is currently available for its intended use or operation.
- 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_69a88aa979788190ad6500f1d8eee2fc |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0e8d5648190915ff689c7ca42bc |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.