Triple
T15774022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verband der Hafenarbeiter |
E382439
|
entity |
| Predicate | Tätigkeitsbereich |
P111844
|
FINISHED |
| Object | Häfen |
—
|
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: Häfen | Statement: [Verband der Hafenarbeiter, Tätigkeitsbereich, Häfen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Tätigkeitsbereich Context triple: [Verband der Hafenarbeiter, Tätigkeitsbereich, Häfen]
-
A.
area of activity
chosen
Indicates the domain, field, or sphere in which an entity is active or carries out its primary functions or operations.
-
B.
placeOfBusinessActivity
Indicates the type or nature of business activity that is conducted at a particular place or location.
-
C.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
D.
occupationalRootActivity
Indicates that an occupation is fundamentally based on or derived from a particular core activity or type of work.
-
E.
competenceArea
Indicates that one entity has a particular domain, field, or area in which it possesses competence, expertise, or responsibility.
- 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.