Triple
T31672120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poland–Ukraine border |
E808297
|
entity |
| Predicate | memberSide |
P190064
|
FINISHED |
| Object | European Union |
—
|
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: European Union | Statement: [Poland–Ukraine border, memberSide, European Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberSide Context triple: [Poland–Ukraine border, memberSide, European Union]
-
A.
memberStateSide1
Indicates that an entity participates as the first member state (or party) on one side of a bilateral or multilateral relationship or agreement.
-
B.
memberOwned
Indicates that an entity is owned collectively by its members rather than by external owners or shareholders.
-
C.
memberFrom
Indicates that an entity is a member originating from, or associated with, a particular source, group, or location.
-
D.
membersServe
Indicates that the members of a group perform services or duties for, or on behalf of, another entity or organization.
-
E.
membershipBy
Indicates that one entity holds membership or belongs to a group, organization, or collection defined by another entity.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: April 30, 2026, 11:01 p.m.