Triple

T18145484
Position Surface form Disambiguated ID Type / Status
Subject Yodel E434376 entity
Predicate hasCompetitor P1375 FINISHED
Object FedEx NE NERFINISHED

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: [Yodel, hasCompetitor, FedEx]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FedEx
Context triple: [Yodel, 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 (2 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_69d8b90aac308190801e2c57d8c5bfe5 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4de33921c8190b6f645ca63fd146b completed April 19, 2026, 1:52 p.m.
Created at: April 10, 2026, 10:29 a.m.