Triple
T17997237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civic Platform |
E430532
|
entity |
| Predicate | hasFormerMembers |
P1168
|
FINISHED |
| Object | past member of Civic Platform |
—
|
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: past member of Civic Platform | Statement: [Civic Platform, hasFormerMembers, past member of Civic Platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerMembers Context triple: [Civic Platform, hasFormerMembers, past member of Civic Platform]
-
A.
hasNotableFormerMemberRole
Indicates that an entity has a role or position that was notably held by a former member of that entity.
-
B.
formerMemberOf
chosen
Indicates that an entity once belonged to or was affiliated with a group, organization, or body, but is no longer a member.
-
C.
hasFormerStaffMember
Indicates that an entity once had a person as a staff member, but that person is no longer employed there.
-
D.
hadNumberOfMembers
Indicates that an entity possessed or was associated with a specific count of members at a given time or in a given context.
-
E.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b3e5c63c8190890436366c4a47c5 |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.