Triple

T13426027
Position Surface form Disambiguated ID Type / Status
Subject Opel Rocks-e E313483 entity
Predicate cargoVariantUse P39014 FINISHED
Object last-mile urban delivery (Rocks-e Kargo) 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: last-mile urban delivery (Rocks-e Kargo) | Statement: [Opel Rocks-e, cargoVariantUse, last-mile urban delivery (Rocks-e Kargo)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cargoVariantUse
Context triple: [Opel Rocks-e, cargoVariantUse, last-mile urban delivery (Rocks-e Kargo)]
  • A. usedInVariant chosen
    Indicates that something (such as a component, feature, or element) is utilized or included within a particular variant or version of a larger entity.
  • B. exportVariantOf
    Indicates that one entity is an exported version or externally released form derived from another, original entity.
  • C. developmentVariant
    Indicates that one entity is a variant or alternative form of another in the context of development (e.g., a different developmental version, configuration, or pathway).
  • D. hasVariant
    Indicates that one entity exists as an alternative form, version, or variation of another entity.
  • E. cargo
    Indicates that one entity is the goods or load being transported, carried, or shipped by 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_69d806ad0c44819088833ae1ec9e9690 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaed066408190a416880affd8416e completed April 12, 2026, 2:40 p.m.
PD Predicate disambiguation batch_69d9a0355de48190bb3fb96912e20df3 completed April 11, 2026, 1:13 a.m.
Created at: April 9, 2026, 9:40 p.m.