Triple
T20314362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DB Schenker |
E510340
|
entity |
| Predicate | offersMultimodalSolutions |
P71966
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [DB Schenker, offersMultimodalSolutions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersMultimodalSolutions Context triple: [DB Schenker, offersMultimodalSolutions, yes]
-
A.
offersSolution
Indicates that one entity provides or proposes a remedy, answer, or way to resolve a problem or need experienced by another entity.
-
B.
offersModality
chosen
Indicates that one entity provides or supports a particular mode, method, or form in which something can be experienced, delivered, or performed.
-
C.
offersTechnology
Indicates that one entity provides or makes available a technology or technological solution to another entity.
-
D.
offersServiceIn
Indicates that a provider makes a particular service available within a specified location or jurisdiction.
-
E.
modeOfService
Indicates the manner, method, or channel through which a service is delivered or provided.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67745e2448190b5611382fe338bb2 |
completed | April 20, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.