Triple
T27244381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Accession 2003 (Poland to the EU) |
E687297
|
entity |
| Predicate | accedingState |
P162275
|
FINISHED |
| Object | 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: Republic of Poland | Statement: [Treaty of Accession 2003 (Poland to the EU), accedingState, Republic of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accedingState Context triple: [Treaty of Accession 2003 (Poland to the EU), accedingState, Republic of Poland]
-
A.
admittedState
Indicates that an entity has been formally accepted or allowed into a particular state or condition.
-
B.
admissionState
Indicates the status or phase of an entity’s admission process within a system or institution.
-
C.
acceptsStateOn
Indicates that an entity agrees to or is configured to receive and handle a specified state or status from another entity or process.
-
D.
admittedStateFormed
Indicates that a political entity was formally accepted into and became part of an already existing state or union.
-
E.
arrivalState
Indicates the condition or status an entity is in upon its arrival at a particular place, time, or context.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6267fcc908190ade3904e25cbcfef |
completed | May 2, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 10:40 a.m.