Triple
T24988822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curator at Museum Folkwang |
E625392
|
entity |
| Predicate | employedInSector |
P62538
|
FINISHED |
| Object | cultural sector |
—
|
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: cultural sector | Statement: [Curator at Museum Folkwang, employedInSector, cultural sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employedInSector Context triple: [Curator at Museum Folkwang, employedInSector, cultural sector]
-
A.
hasOccupationSector
chosen
Indicates that an entity’s occupation belongs to or is categorized within a particular economic or professional sector.
-
B.
employedTo
Indicates that one entity is hired or engaged to perform work, services, or duties for another entity.
-
C.
employmentBasedCategory
Indicates that one entity’s classification or status is determined by its relationship to employment, such as being based on a specific job, role, or work-related category.
-
D.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
E.
employedUnder
Indicates that one entity works as an employee under the authority, supervision, or organizational structure of another entity.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44a42f61c8190bcb01ceec1f889b1 |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:03 a.m.