Triple
T7698640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Tribunal of Poland |
E174430
|
entity |
| Predicate | proceedingsInitiatedBy |
P1408
|
FINISHED |
| Object | Sejm resolution |
—
|
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: Sejm resolution | Statement: [State Tribunal of Poland, proceedingsInitiatedBy, Sejm resolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proceedingsInitiatedBy Context triple: [State Tribunal of Poland, proceedingsInitiatedBy, Sejm resolution]
-
A.
typeOfProceedings
Indicates the specific category or kind of legal or formal process under which an action or case is being conducted.
-
B.
proceedingsAre
Indicates that certain events, actions, or legal steps constitute or are recognized as formal proceedings.
-
C.
initiatedBy
chosen
Indicates that an action, event, or process was started or set in motion by a particular entity.
-
D.
legalProcedureUsed
Indicates that a particular legal procedure or process is applied or employed in relation to a case, action, or legal matter.
-
E.
possiblyInitiatedBy
Indicates that an event or state may have been initiated or caused by a particular entity, but this initiating role is uncertain or not definitively established.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.