Triple
T16265805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPS |
E394871
|
entity |
| Predicate | hasCompetitor |
P1375
|
FINISHED |
| Object | FedEx |
E4793
|
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: FedEx | Statement: [UPS, hasCompetitor, FedEx]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FedEx Context triple: [UPS, hasCompetitor, FedEx]
-
A.
FedEx
chosen
FedEx is a global courier delivery services company known for its overnight shipping and pioneering real-time package tracking.
-
B.
United Parcel Service (UPS)
United Parcel Service (UPS) is a global package delivery and supply chain management company known for its extensive logistics network and brown delivery trucks.
-
C.
TNT Express
TNT Express is an international courier and logistics company known for its global parcel delivery and express mail services.
-
D.
StarTrack
StarTrack is an Australian logistics and freight company specializing in parcel delivery and express transport services.
-
E.
DHL
DHL is a global logistics and courier company known for its international express mail, freight transportation, and supply chain management services.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c839788190b974d1d0d2525b88 |
completed | April 17, 2026, 2:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a001f8eac988190bdcba6778fbffd64 |
completed | May 10, 2026, 6:02 a.m. |
Created at: April 10, 2026, 5:05 a.m.