Triple
T37767728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1981 Accession Treaty |
E941460
|
entity |
| Predicate | resultedInMembershipOf |
P34367
|
FINISHED |
| Object | European Communities |
—
|
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 Communities | Statement: [1981 Accession Treaty, resultedInMembershipOf, European Communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultedInMembershipOf Context triple: [1981 Accession Treaty, resultedInMembershipOf, European Communities]
-
A.
membershipIn
Indicates that an entity belongs to, is part of, or holds membership in a particular group, organization, or collection.
-
B.
impliesMembershipIn
Indicates that one entity logically entails or asserts that another entity belongs to a particular group, set, or category.
-
C.
confersMembershipIn
chosen
Indicates that one entity grants or bestows membership status in a group, organization, or category upon another entity.
-
D.
membershipConsistsOf
Indicates that a membership is composed of, or includes, specific member entities as its constituents.
-
E.
membershipBy
Indicates that one entity holds membership or belongs to a group, organization, or collection defined by another entity.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 3, 2026, 4:19 p.m.