Triple
T15382072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roshen Klaipėda factory |
E367827
|
entity |
| Predicate | hasWorkShiftType |
P104843
|
FINISHED |
| Object | shift work |
—
|
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: shift work | Statement: [Roshen Klaipėda factory, hasWorkShiftType, shift work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkShiftType Context triple: [Roshen Klaipėda factory, hasWorkShiftType, shift work]
-
A.
hasWorkSchedule
Indicates that an entity is assigned or follows a specific work schedule, defining when they are expected to work.
-
B.
hasWorkforceType
Indicates the type or category of workforce associated with an entity (such as permanent, temporary, contract, or part-time).
-
C.
hasRoleInWorkType
Indicates that an entity holds a specific role or function within a particular type or category of work.
-
D.
hasWorkTypeRelation
chosen
Indicates a relationship specifying the type or category of work associated with an entity.
-
E.
hasNumberOfShifts
Indicates the quantity of work shifts associated with a given 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e61928c81908852c355d537ed9c |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.