Triple
T3829197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DHL |
E88768
|
entity |
| Predicate | fullName |
P16
|
FINISHED |
| Object | DHL Express |
E88768
|
NE 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: DHL Express | Statement: [DHL, fullName, DHL Express]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DHL Express Context triple: [DHL, fullName, DHL Express]
-
A.
DHL
DHL is the Dag Hammarskjöld Library, the United Nations’ main research and information resource center located at its headquarters in New York.
-
B.
DHL
chosen
DHL is a global logistics and courier company known for its international express mail, freight transportation, and supply chain management services.
-
C.
National Express
National Express is a major UK-based coach and bus operator providing long-distance and local passenger transport services domestically and internationally.
-
D.
Channel Express
Channel Express was a British airline that operated cargo and passenger services before rebranding and evolving into the low-cost carrier Jet2.com.
-
E.
FedEx
FedEx is a global courier delivery services company known for its overnight shipping and pioneering real-time package tracking.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb683c2081908ffa6e759a3470fe |
completed | March 9, 2026, 3:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4fb54636c8190a46224e0a8215e26 |
completed | March 14, 2026, 6:08 a.m. |
Created at: March 9, 2026, 3:17 p.m.