Triple
T1290905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FDX |
E27543
|
entity |
| Predicate | represents |
P129
|
FINISHED |
| Object | FedEx Corporation |
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 Corporation | Statement: [FDX, represents, FedEx Corporation]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FedEx Corporation Context triple: [FDX, represents, FedEx Corporation]
-
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.
YRC Worldwide
YRC Worldwide is a large American less-than-truckload (LTL) freight transportation and logistics company headquartered in Overland Park, Kansas.
-
D.
DHL
DHL is the Dag Hammarskjöld Library, the United Nations’ main research and information resource center located at its headquarters in New York.
-
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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d6af908190ade9c481cc6f0ad8 |
completed | March 1, 2026, 10:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acacbf0cf48190937f620900b08d3f |
completed | March 7, 2026, 10:54 p.m. |
Created at: March 1, 2026, 7:51 p.m.