Triple
T699903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First-Class Mail |
E13974
|
entity |
| Predicate | priorityLevel |
P7279
|
FINISHED |
| Object | higher than USPS Marketing Mail |
—
|
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: higher than USPS Marketing Mail | Statement: [First-Class Mail, priorityLevel, higher than USPS Marketing Mail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priorityLevel Context triple: [First-Class Mail, priorityLevel, higher than USPS Marketing Mail]
-
A.
policyLevel
Indicates the degree or tier of strictness, scope, or priority associated with a given policy.
-
B.
designationLevel
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
C.
logicalLevel
Indicates the relative position or depth of something within a hierarchy of abstraction, reasoning, or logical structure.
-
D.
representedLevel
Indicates that one entity denotes or encodes the degree, intensity, or value (i.e., the level) of another entity or property.
-
E.
classificationLevel
chosen
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a544e3608190ac315c7aa9f88e7e |
completed | March 1, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ec8c748190b198492a0eea4445 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.