Triple
T699990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Media Mail |
E13976
|
entity |
| Predicate | inspectionPolicy |
P1051
|
FINISHED |
| Object | subject to postal inspection |
—
|
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: subject to postal inspection | Statement: [Media Mail, inspectionPolicy, subject to postal inspection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspectionPolicy Context triple: [Media Mail, inspectionPolicy, subject to postal inspection]
-
A.
isInspected
Indicates that an entity is examined or checked by another entity to assess its condition, quality, or compliance.
-
B.
issuesPolicyOn
Indicates that an authority or organization formally creates, approves, or enacts a policy concerning a particular subject or domain.
-
C.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
-
D.
policyImplication
Indicates that one policy, decision, or condition leads to, justifies, or necessitates another policy outcome or course of action.
-
E.
governingPolicy
chosen
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of 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_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.