Triple
T10127592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Fatherland Party |
E226252
|
entity |
| Predicate | hadPeakMembership |
P45752
|
FINISHED |
| Object | about 1,250,000 members |
—
|
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: about 1,250,000 members | Statement: [German Fatherland Party, hadPeakMembership, about 1,250,000 members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPeakMembership Context triple: [German Fatherland Party, hadPeakMembership, about 1,250,000 members]
-
A.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
B.
hadNumberOfMembers
chosen
Indicates that an entity possessed or was associated with a specific count of members at a given time or in a given context.
-
C.
hasMemberWhoBecame
Indicates that a group or organization includes at least one member who later attained or transitioned into a specified role, status, or affiliation.
-
D.
membershipPeak
Indicates the time or period at which an entity’s membership in a group or organization reaches its highest level.
-
E.
hadPeakInfluencePeriod
Indicates the time span during which an entity exerted its greatest or most significant influence.
- 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2f0a0e881909267a83fbeb31f0c |
completed | April 2, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:05 p.m.