Triple
T27209451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trybunał Stanu |
E683957
|
entity |
| Predicate | canBeMotionedBy |
P177516
|
FINISHED |
| Object | Sejm of the Republic of Poland |
—
|
NE NERFINISHED |
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 of the Republic of Poland | Statement: [Trybunał Stanu, canBeMotionedBy, Sejm of the Republic of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeMotionedBy Context triple: [Trybunał Stanu, canBeMotionedBy, Sejm of the Republic of Poland]
-
A.
canMove
Indicates that one entity has the ability or permission to change its location or position relative to its environment or another entity.
-
B.
usesMovement
Indicates that an entity performs or involves some form of movement as part of its action or behavior.
-
C.
hasVerticalMotion
Indicates that an entity is undergoing or exhibiting motion in the vertical direction (upward or downward).
-
D.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
movementSupported
Indicates that an entity’s movement is enabled, facilitated, or allowed by another entity or system.
- F. None of above. chosen
Provenance (4 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 27, 2026, 9:39 a.m.