Triple
T35727006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | extraordinary sejm |
E1032641
|
entity |
| Predicate | conveningReason |
P39907
|
FINISHED |
| Object | foreign invasion |
—
|
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: foreign invasion | Statement: [extraordinary sejm, conveningReason, foreign invasion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conveningReason Context triple: [extraordinary sejm, conveningReason, foreign invasion]
-
A.
convenedFor
chosen
Indicates that an event, meeting, or gathering was brought together for a specific purpose, topic, or beneficiary.
-
B.
conveningCondition
Indicates the circumstances or requirements under which a meeting, gathering, or formal session is initiated or brought together.
-
C.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
D.
convenedIn
Indicates that an event, meeting, or formal gathering was brought together and held at a specific location.
-
E.
convenes
Indicates bringing people or groups together to formally meet, discuss, or deliberate on a particular matter.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:05 p.m.