Triple
T18034345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GUE/NGL |
E431467
|
entity |
| Predicate | hasMemberPartiesFrom |
P6048
|
FINISHED |
| Object | multiple European Union member states |
—
|
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: multiple European Union member states | Statement: [GUE/NGL, hasMemberPartiesFrom, multiple European Union member states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberPartiesFrom Context triple: [GUE/NGL, hasMemberPartiesFrom, multiple European Union member states]
-
A.
hasMemberParty
chosen
Indicates that a group, organization, or coalition includes a specific party as one of its members.
-
B.
hasHadMemberFromParty
Indicates that an entity (such as an organization or group) has, at some point in time, included at least one member affiliated with a specified political party.
-
C.
hasPartyMember
Indicates that a particular individual is a member or participant of a specified party or group.
-
D.
hasNumberOfParties
Indicates the total count of distinct parties or participants involved in a given relationship, agreement, or event.
-
E.
arePartyTo
Indicates that the entities are participants or signatories in the same agreement, contract, or legal arrangement.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be38766c8190ae95701f4575469c |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.