Triple
T29819997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poland–Belarus border |
E757218
|
entity |
| Predicate | memberStateOnOneSide |
P17966
|
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–Belarus border, memberStateOnOneSide, European Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberStateOnOneSide Context triple: [Poland–Belarus border, memberStateOnOneSide, 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.
memberStatesAreMemberOf
chosen
Indicates that certain states belong to or hold membership in a particular organization, group, or union.
-
C.
memberStateIntended
Indicates that a particular state is designated or intended to be a member of a specified organization, agreement, or grouping.
-
D.
isMemberStateRelationOf
Indicates that one entity is a member state within, or in a member-state relationship to, another entity such as an organization, union, or federation.
-
E.
notUNMemberState
Indicates that an entity is not a member state of the United Nations.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 29, 2026, 5:28 p.m.