Triple
T15774031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verband der Hafenarbeiter |
E382439
|
entity |
| Predicate | Mitgliedschaft |
P27891
|
FINISHED |
| Object | freiwillig |
—
|
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: freiwillig | Statement: [Verband der Hafenarbeiter, Mitgliedschaft, freiwillig]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Mitgliedschaft Context triple: [Verband der Hafenarbeiter, Mitgliedschaft, freiwillig]
-
A.
membershipIn
chosen
Indicates that an entity belongs to, is part of, or holds membership in a particular group, organization, or collection.
-
B.
clubMembership
Indicates that an entity belongs to, is enrolled in, or holds membership status within a particular club.
-
C.
membershipBy
Indicates that one entity holds membership or belongs to a group, organization, or collection defined by another entity.
-
D.
membershipField
Indicates that one entity serves as a field or attribute capturing the membership status or association of another entity within a group, organization, or collection.
-
E.
membershipBased
Indicates that access, participation, or inclusion in something is conditional on holding a membership or belonging to a defined group.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05198c1588190a65e23c18443eb5c |
completed | April 16, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.