Triple
T16835045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MASkargo |
E409252
|
entity |
| Predicate | specialCargoService |
P93658
|
FINISHED |
| Object | perishable goods handling |
—
|
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: perishable goods handling | Statement: [MASkargo, specialCargoService, perishable goods handling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialCargoService Context triple: [MASkargo, specialCargoService, perishable goods handling]
-
A.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
B.
hasCargoServices
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
-
C.
commercialCargoProvider
Indicates that an entity serves as a provider of commercial cargo transport or delivery services for another entity.
-
D.
cargoSpecialization
chosen
Indicates that an entity is specialized or designated for handling, transporting, or managing a particular type or category of cargo.
-
E.
primaryCargoProtected
Indicates that the main cargo associated with an entity is safeguarded or shielded from harm, loss, or interference.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b31aa44c8190b4f402f1898e6998 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.