Triple
T26625229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sligro Food Group |
E668321
|
entity |
| Predicate | hasLogisticsActivity |
P28699
|
FINISHED |
| Object | warehousing |
—
|
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: warehousing | Statement: [Sligro Food Group, hasLogisticsActivity, warehousing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLogisticsActivity Context triple: [Sligro Food Group, hasLogisticsActivity, warehousing]
-
A.
hasLogisticalRole
Indicates that an entity holds a responsibility or function related to planning, coordinating, or managing logistical operations or resources.
-
B.
logisticsFeature
chosen
Indicates that something possesses a characteristic, capability, or function specifically related to logistics operations or processes.
-
C.
logisticsSegment
Indicates a distinct portion or leg of a broader logistics or transportation process that connects two stages in the movement of goods or resources.
-
D.
usedLogisticsRoute
Indicates that a particular logistics route was employed to transport or move goods or resources between locations.
-
E.
hasShippingLaneType
Indicates the specific category or type of shipping lane associated with a given route or area.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 2:22 a.m.