Triple
T3838002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPS Worldwide Express |
E91181
|
entity |
| Predicate | includesTrackingNumber |
P52306
|
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: [UPS Worldwide Express, includesTrackingNumber, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTrackingNumber Context triple: [UPS Worldwide Express, includesTrackingNumber, yes]
-
A.
isTrackedBy
Indicates that an entity’s state, behavior, or changes are being monitored, recorded, or followed by another entity.
-
B.
trailNumber
Indicates that an entity is associated with a specific trail identifier or route number within a trail system.
-
C.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
-
D.
trackingType
Indicates the method or category by which an entity’s movement, status, or progress is monitored or recorded.
-
E.
containsShippingRoute
Indicates that one location or area includes within its boundaries a shipping route used for transporting goods or vessels.
- F. None of above. chosen
Provenance (4 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb9d11f081909fc51e84657ec7f1 |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb828fb08190901d51edbe8bd304 |
completed | March 9, 2026, 3:47 p.m. |
Created at: March 9, 2026, 3:18 p.m.