Triple
T16981346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPS brand identity |
E411951
|
entity |
| Predicate | keyMessageTheme |
P100509
|
FINISHED |
| Object | reliable delivery |
—
|
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: reliable delivery | Statement: [UPS brand identity, keyMessageTheme, reliable delivery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyMessageTheme Context triple: [UPS brand identity, keyMessageTheme, reliable delivery]
-
A.
keyThemeIn
Indicates that a particular theme is a central or primary thematic focus within a given work, context, or subject.
-
B.
themeKey
chosen
Indicates that one entity serves as the primary subject, topic, or thematic focus associated with another entity.
-
C.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
D.
signatureTheme
Indicates that something serves as a distinctive, defining theme strongly associated with a particular entity or context.
-
E.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
- F. None of above.
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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d18776c081909225620fd43aca57 |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.