Triple
T699993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Media Mail |
E13976
|
entity |
| Predicate | trackingAvailability |
P5871
|
FINISHED |
| Object | USPS Tracking included |
—
|
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: USPS Tracking included | Statement: [Media Mail, trackingAvailability, USPS Tracking included]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackingAvailability Context triple: [Media Mail, trackingAvailability, USPS Tracking included]
-
A.
availability
Indicates that an entity is present, accessible, or ready for use or interaction by another entity.
-
B.
trackUsage
Indicates that one entity monitors and records how another entity or resource is being used over time.
-
C.
serviceAvailability
chosen
Indicates whether a particular service is accessible and operational for use during a given time or under specified conditions.
-
D.
seekerCapability
Indicates that an entity has the ability or function to detect, track, or locate a target or object.
-
E.
track
Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
- 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.